deploy/deploy-dev.sh deploys the test instance to home.siebens.org behind its
existing Caddy: from your machine, over one SSH session, it fetches the pushed
branch, builds, migrates explicitly, restarts web, and waits for /healthz.
- A hard reset to origin/<branch>, not a pull: a deploy target only receives
deploys, so it should match the branch exactly rather than risk a merge conflict
from drift no one meant to leave on the server.
- Refuses to deploy a branch with unpushed local commits — the server pulls from
git, so that would ship stale code without saying so.
- Migrations run explicitly (dc run --rm web migrate), never from the entrypoint,
and only `web` is recreated so db/redis keep running.
- Fails loudly if .env.production or .env is missing rather than booting a
half-configured stack, and dumps recent web logs if the health check never passes.
Host/user/dir/branch all override via env vars. Documented in DEPLOYMENT.md with
the first-time server setup.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
