fix(ci): build staging images with isolated public settings
Merged
PR
5d ago+166+166+012345678901234567890123456789-28-28-01234567890123456789
Staging still builds on the application VPS and bakes in the temporary hostname. Allow the manual container workflow on staging with its own branch-restricted GitHub environment and validate its final URL, app environment and Clerk key before publishing. Add CI coverage for those checks and document the backup, approval and migration gates before deployment.
Validation: eight focused configuration tests, actual staging configuration through the workflow CLI, type checking and 2,104 passing unit tests. Lint has 79 existing warnings and no errors. Image publishing does not deploy or change DNS.
Summary by CodeRabbit
- New Features
- Container images can now be built for both
masterandstaging, with settings selected for each branch. The workflow publishes an image without deploying it or applying database migrations.
- Container images can now be built for both
- Documentation
- Updated self-hosting and container-image guides with build and deployment steps, including immutable image digests, pull credentials, and migration and backup checks before deployment. Also clarified that existing Vercel deployments remain in place until retirement is approved.