fix production issue

command_to_run_dev.txt

@@ -21,4 +21,26 @@ docker compose -f docker-compose.dev.yml --profile full up --build will no longe
 Your data stays as long as you do not run docker compose ... down -v or manually delete the Docker volumes.
 If you later change the schema and want to apply it without wiping data, run:
 docker compose -f docker-compose.dev.yml run --rm migrate sh -c "npm run db:deploy"
-Production was already using a persistent named Postgres volume, so the main issue was the dev bootstrap behavior. Restart the dev stack once for this change to take effect.
+Production was already using a persistent named Postgres volume, so the main issue was the dev bootstrap behavior. Restart the dev stack once for this change to take effect.
+
+
+
+
+
+
+
+
+Done. The DOCKER.md production section now covers the full deployment flow from a fresh server. The short version:
+
+
+# Once per server
+docker network create traefik-proxy
+
+# Clone & configure
+git clone <repo> rentaldrivego && cd rentaldrivego
+cp .env.docker.production.example .env.docker.production
+# → fill in POSTGRES_PASSWORD, JWT_SECRET, ACME_EMAIL, RESEND_API_KEY
+
+# Deploy
+docker compose -f traefik.yaml up -d
+docker compose -f docker-compose.production.yml up --build -d