25 lines
1.6 KiB
Markdown
25 lines
1.6 KiB
Markdown
## 1. Discovery And Current State
|
|
|
|
- [ ] 1.1 Identify current deploy target and mechanism (compose/swarm/k8s, image vs files) and document constraints in `README` or `ops/` docs
|
|
- [ ] 1.2 Identify the content source(s) that define "latest content" (e.g., WordPress/API) and how builds currently fetch content
|
|
- [ ] 1.3 Confirm current build output (static assets) and runtime server (e.g., nginx) requirements
|
|
|
|
## 2. Build And Publish A Deployable Artifact
|
|
|
|
- [ ] 2.1 Ensure the repo can produce a deterministic production build inside CI (no host dependencies)
|
|
- [ ] 2.2 Create or update a Dockerfile to build the site and package the built output into a runtime image
|
|
- [ ] 2.3 Add build metadata to the image (tagging convention and/or embedded version file)
|
|
- [ ] 2.4 Configure CI to build and publish the image to a registry accessible by the server
|
|
|
|
## 3. Server-Side Docker-Only Refresh Workflow
|
|
|
|
- [ ] 3.1 Add or update the server Docker Compose/service definition to run the published image
|
|
- [ ] 3.2 Add documented operator commands to refresh to the latest image (pull + restart)
|
|
- [ ] 3.3 Add a verification command/procedure to show the currently deployed version (tag/digest/build metadata)
|
|
- [ ] 3.4 Define rollback procedure to re-deploy a previous known-good tag/digest
|
|
|
|
## 4. Validation
|
|
|
|
- [ ] 4.1 Validate a refresh on a test/staging server: pull latest image, restart, confirm content changes are visible
|
|
- [ ] 4.2 Validate failure mode: simulate pull failure and confirm the existing site remains serving
|
|
- [ ] 4.3 Update docs with a minimal "runbook" for operators (refresh, verify, rollback) |