Implement manual versioned Synology deployments for S6
All checks were successful
Build, test and publish / verify (push) Successful in 6m34s
All checks were successful
Build, test and publish / verify (push) Successful in 6m34s
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# S6 — Manual versioned production deployment through Gitea
|
||||
|
||||
Status: REFINED
|
||||
Status: IN_PROGRESS
|
||||
|
||||
Agreed after the grill-me interview; shared understanding confirmed.
|
||||
|
||||
@@ -175,3 +175,10 @@ This specification records the confirmed design. Implementing workflows, release
|
||||
automation, Compose configuration, Synology provisioning and collecting actual
|
||||
deployment/recovery evidence are subsequent work. Configuration alone does not
|
||||
complete S6.
|
||||
|
||||
Implementation is in progress on `feature/S6_deployment`: workflows, Compose,
|
||||
release/retry/rollback helpers, failure-path tests and provisioning/runbook are
|
||||
provided. The dedicated NAS account, registry login and Gitea deployment secrets
|
||||
are provisioned. Real image preparation passed without a release or container
|
||||
replacement. See `docs/s6-validation.md`; workflow execution and production
|
||||
deployment/recovery evidence remain required after the protected main merge.
|
||||
Reference in New Issue
Block a user