fix prod

production/README.md

@@ -57,7 +57,7 @@ If the registry is only reachable inside a VPN container, use the shared archive
 IMAGE_ARCHIVE_DIR=/opt/docker-image-transfer
 IMAGE_ARCHIVE_REQUIRED=true
 APP_IMAGE=10.0.0.4/melabidi/carmanagement
-IMAGE_TAG=13d0512048d86e9fe93e9395459d04663c2b7eb0
+IMAGE_TAG=latest
 REGISTRY_USER=melabidi
 ```
 
@@ -67,13 +67,19 @@ From the VPS, use the VPN container network to copy the image into the transfer
 VPN_CONTAINER="6c5dca44e1c2" ./fetch-image-through-vpn.sh
 ```
 
+Or fetch the archive and deploy in one command:
+
+```bash
+VPN_CONTAINER="6c5dca44e1c2" ./deploy-production.sh --fetch-through-vpn
+```
+
 Equivalent manual command:
 
 ```bash
 sudo mkdir -p /opt/docker-image-transfer
 sudo chmod 700 /opt/docker-image-transfer
 
-IMAGE_TAG="13d0512048d86e9fe93e9395459d04663c2b7eb0"
+IMAGE_TAG="latest"
 REGISTRY_USER="melabidi"
 VPN_CONTAINER="6c5dca44e1c2"
 
@@ -95,6 +101,12 @@ docker run --rm \
 
 Set the same `IMAGE_TAG` in `.env.docker.production`, then run the deployment. The deploy script will run `docker load -i /opt/docker-image-transfer/carmanagement-${IMAGE_TAG}.tar` before starting services. Because `IMAGE_ARCHIVE_REQUIRED=true`, the VPS will not try to pull from `10.0.0.4` directly.
 
+If the VPS can reach the registry directly and you want to bypass archive loading, run:
+
+```bash
+./deploy-production.sh --image-tag latest --pull-registry
+```
+
 ## Deploy A Prebuilt Release
 
 ```bash