Sync the self-hosting stack

docker-compose.yml

@@ -206,6 +206,15 @@ services:
       AGENT_HEARTBEAT_INTERVAL_SEC: ${AGENT_HEARTBEAT_INTERVAL_SEC:-30}
       RUN_SHUTDOWN_GRACE_SEC: ${RUN_SHUTDOWN_GRACE_SEC:-25}
 
+      # This container brings the database up to its own schema before serving. Left on, because on
+      # compose one container IS the deployment. Turn it off only where something else runs
+      # `migrate.sh` first — an orchestrator with a run-once Job, say.
+      JARVIS_SKIP_MIGRATIONS: ${JARVIS_SKIP_MIGRATIONS:-false}
+      # Let that phase DROP columns and tables. OFF, and it should stay off between deliberate acts:
+      # without it the schema sync REFUSES and prints what it would have destroyed, which is the
+      # answer you want from an upgrade that was not expecting to lose anything.
+      SCHEMA_ACCEPT_DATA_LOSS: ${SCHEMA_ACCEPT_DATA_LOSS:-false}
+
       # Where the agent binaries live, if you have them. Leaving this unset is a supported state:
       # everything except the agent installer works, and the installer answers 503 saying no build is
       # published. See the README — a self-hosted instance has no way to produce these.
@@ -230,7 +239,7 @@ services:
     ports:
       # Put your own TLS terminator in front of this. Jarvis speaks plain HTTP here on purpose and
       # reads X-Forwarded-Proto to know what the browser actually used.
-      - "${JARVIS_PORT:-8080}:80"
+      - "${JARVIS_PORT:-8080}:8080"
 
 volumes:
   postgres_data: