Set up continuous deployment (CD) via Forgejo Actions #12

New issue

Closed

opened 2026-06-23 23:15:09 +00:00 by rbrooks · 0 comments

rbrooks commented

2026-06-23 23:15:09 +00:00

Owner

Target release: v1.1.0

Build on the CI pipeline (see "Set up Forgejo Actions CI pipeline") to deploy merged main automatically. Today deploys are manual over SSH (see docs/HANDOFF.md).

Candidate scope

Build and push the app image to the Forgejo package registry.
Auto-deploy to dev on merge to main; deploy to prod on tag/release.
Run Alembic migrations as part of deploy (already automatic on container start via lifespan).
Environment protection / manual approval gate for prod.

Source: user request; docs/HANDOFF.md deployment commands.

**Target release:** v1.1.0 Build on the CI pipeline (see "Set up Forgejo Actions CI pipeline") to deploy merged `main` automatically. Today deploys are manual over SSH (see `docs/HANDOFF.md`). **Candidate scope** - [ ] Build and push the app image to the Forgejo package registry. - [ ] Auto-deploy to dev on merge to `main`; deploy to prod on tag/release. - [ ] Run Alembic migrations as part of deploy (already automatic on container start via lifespan). - [ ] Environment protection / manual approval gate for prod. Source: user request; `docs/HANDOFF.md` deployment commands.

rbrooks added the

area:ci-cd

type:infra

v1.1.0

labels

2026-06-23 23:16:42 +00:00

rbrooks added this to the v1.1.0 - Operations & observability (+ CD) milestone

2026-06-23 23:23:16 +00:00

rbrooks referenced this issue

2026-06-24 00:32:14 +00:00

Show app version in UI with update-available check against Forgejo #27

rbrooks referenced this issue