34 lines
1.4 KiB
Markdown
34 lines
1.4 KiB
Markdown
# Deployment ownership
|
|
|
|
Movie Night application code belongs to this repository. Its production
|
|
deployment definition is governed by the private Gitea repository
|
|
`kbondelie/server-infrastructure`, currently referenced as the submodule
|
|
`stacks/bondelie-media/movie-night`.
|
|
|
|
## Current transitional path
|
|
|
|
Production on `bondelie-media` still builds this repository's Dockerfile
|
|
locally. Until the registry pipeline is implemented:
|
|
|
|
1. Commit and push application changes here.
|
|
2. Advance the Movie Night submodule pointer in `server-infrastructure`.
|
|
3. Review and merge that infrastructure change.
|
|
4. Synchronize only the declared application source to the host and run the
|
|
documented manual Compose build/deployment.
|
|
5. Verify the HTTP endpoint and container health.
|
|
|
|
Do not make production-only source edits. The host `.env` and SQLite data are
|
|
runtime state and must never be committed.
|
|
|
|
## Intended path
|
|
|
|
After Renovate is operational, Gitea Actions will test this repository and
|
|
publish semantic-version images to the private Gitea OCI registry. Production
|
|
Compose will change from `build: .` to a pinned
|
|
`version@sha256:registry-digest` image in `server-infrastructure`. Renovate
|
|
will propose releases there; a human merge and Ansible deployment will remain
|
|
the production gates.
|
|
|
|
The active sequencing and safety requirements live in
|
|
`server-infrastructure/docs/implementation-plan.md`.
|