S6: manual versioned Synology deployment #12

wanjakrah · 2026-11-03T14:18:02+01:00

wanjakrah commented

2026-11-03 14:18:02 +01:00

Production releases need a deliberate deployment action after a successful main build. This adds manual Gitea release/retry/rollback workflows, shared semantic version Git tags and a digest-pinned Synology Compose stack. The coordinator verifies successful main-build provenance, serializes mutations on the NAS, rejects stale/duplicate releases and restores the prior image pair after failed health checks.

The dedicated NAS SSH account, separate registry pull credential and Gitea deployment settings are provisioned. A real DS224+ probe retrieved both verified main images and validated Compose, stopping before tag creation or container replacement. S6 remains IN_PROGRESS: actual main-dispatched deployment, recovery and rollback evidence follows the protected merge. Deployment may erase application data until S16.

Validation:

Full Gitea feature build #36 passed for implementation commit 525e9f9335, including Maven verification, frontend checks/build, Docker builds and container E2E.
17 existing CI behavior tests and 32 release tests passed, including the actual POSIX script with isolated command adapters.
Palantir formatting check, shell syntax, workflow YAML/trigger checks and Compose validation passed.
Real NAS SSH, Docker permissions, registry login, preflight and image preparation verified; no production release created.

The final documentation-only evidence commit uses the accepted [skip ci] marker and leaves the verified implementation unchanged. Operational instructions and acceptance evidence are in docs/production-deployment.md and docs/s6-validation.md. Backend/frontend application code is unchanged.

Production releases need a deliberate deployment action after a successful main build. This adds manual Gitea release/retry/rollback workflows, shared semantic version Git tags and a digest-pinned Synology Compose stack. The coordinator verifies successful main-build provenance, serializes mutations on the NAS, rejects stale/duplicate releases and restores the prior image pair after failed health checks. The dedicated NAS SSH account, separate registry pull credential and Gitea deployment settings are provisioned. A real DS224+ probe retrieved both verified main images and validated Compose, stopping before tag creation or container replacement. S6 remains IN_PROGRESS: actual main-dispatched deployment, recovery and rollback evidence follows the protected merge. Deployment may erase application data until S16. Validation: - [Full Gitea feature build #36](http://192.168.2.28:3000/wanjakrah/agiledancers/actions/runs/36) passed for implementation commit 525e9f9335e4343c28f91664c149d24da9284904, including Maven verification, frontend checks/build, Docker builds and container E2E. - 17 existing CI behavior tests and 32 release tests passed, including the actual POSIX script with isolated command adapters. - Palantir formatting check, shell syntax, workflow YAML/trigger checks and Compose validation passed. - Real NAS SSH, Docker permissions, registry login, preflight and image preparation verified; no production release created. The final documentation-only evidence commit uses the accepted [skip ci] marker and leaves the verified implementation unchanged. Operational instructions and acceptance evidence are in docs/production-deployment.md and docs/s6-validation.md. Backend/frontend application code is unchanged.

wanjakrah added 2 commits 2026-11-03 14:18:03 +01:00

refinement of spec S6

Build, test and publish / verify (push) Successful in 5m49s

Details

c9db528756

Implement manual versioned Synology deployments for S6

Build, test and publish / verify (push) Successful in 6m34s

Details

525e9f9335

wanjakrah added 1 commit 2026-11-03 14:49:24 +01:00

Record successful S6 feature build validation [skip ci] 60496de8bb

wanjakrah changed title from ~~WIP: S6 manual versioned Synology deployment~~ to S6: manual versioned Synology deployment