Operations and hosting

The reference deployment uses GitHub Actions, Docker, Caddy, a production MySQL host, and disposable per-PR MySQL databases.

Repository operators should follow the complete hosting guide. It covers DNS, GitHub secrets and environments, VPS bootstrap, deployment, migration compatibility, backups, restore drills, and monitoring.

Release behavior

• CI must succeed before deployment.
• Production is backed up before Drizzle migrations.
• The previous application remains active until the replacement passes database-backed readiness.
• PRs from the repository receive pr-<number> environments and isolated schemas.
• Closing a PR removes its route, container, user, credentials, and database.

Schema migrations must follow expand/contract rules. A container switch is non-disruptive, but destructive or locking SQL can still interrupt the old release.