Production Readiness-checklist andreaslop-site-hosting (test)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-08 00:17:57 +01:00
co-authored by Claude Sonnet 5.5
parent e44cf493f6
commit b60b3138ab
4 changed files with 48 additions and 3 deletions
+2 -2
View File
@@ -7,6 +7,6 @@
| Master CMS Module (master-cms-module) | ✅ Complete | unknown | Modules, Availability | 2026-06-26 |
| Tech Debt Backlog (tech-debt-backlog) | 🔵 Inception | unknown | Modules.Master, Frontend | 2026-07-01 |
| Local Dev Master/Slave Setup (local-dev-master-slave-setup) | ✅ Complete | unknown | Modules.Master, Api, Frontend | 2026-07-02 |
| Gitea Deployment Workflow (gitea-deployment-workflow) | 🟡 Operations | feature/gitea-deployment-workflow | CI/CD, Api (hosting/config), Core, Modules, Frontend (build), Docs | 2026-07-27 |
| Gitea Deployment Workflow (gitea-deployment-workflow) | 🟡 Operations (wacht op CI-proef en eerste test-deploy) | feature/gitea-deployment-workflow | CI/CD, Api (hosting/config), Core, Modules, Frontend (build), Docs | 2026-07-27 |
| SlpSoftware Production API (slpsoftware-api) | ✅ Complete | feature/slpsoftware-api | Clients (new Api.SlpSoftware), Modules (new Offerings module + Tests), Core (CmsHost), CI/CD (retargeted to Api.SlpSoftware) | 2026-08-02 |
| Andrea's site hosting (andreaslop-site-hosting) | 🟡 Operations | feature/andreaslop-site-hosting | Core (CmsHost, CSP, static content), Clients (new Api.AndreaSlopFotografie), Frontend (theme), CI/CD | 2026-11-06 |
| Andrea's site hosting (andreaslop-site-hosting) | 🟡 Operations (wacht op CI-proef en eerste test-deploy) | feature/andreaslop-site-hosting | Core (CmsHost, CSP, static content), Clients (new Api.AndreaSlopFotografie), Frontend (theme), CI/CD | 2026-11-06 |
@@ -5,7 +5,7 @@
- **Feature Slug**: andreaslop-site-hosting
- **Project Type**: Brownfield
- **Start Date**: 2026-11-06T00:06:13Z
- **Current Stage**: OPERATIONS - Monitoring Setup (awaiting approval)
- **Current Stage**: OPERATIONS - Production Readiness (complete; waiting for CI proof and first test deploy)
- **Branch**: feature/andreaslop-site-hosting
- **Request Type**: Feature (two units: U1 core-site-hosting, U2 andreaslop-client)
@@ -56,3 +56,7 @@
### Monitoring Setup
- **Included**: Yes
- **Approach**: Combination (logging + alerting on existing tooling; no new dashboards)
- **Status**: approved 2026-11-08
### Production Readiness
- **Verdict**: Yes with caveats (test only), see operations/production-readiness-checklist.md
@@ -438,3 +438,8 @@
**Timestamp**: 2026-11-08
**User Input (via CMS & API)**: Q1 A, Q2 D, Q3 A, Q4 A, Q5 A. Also: CI proof via workflow_dispatch started by Bryan (option B), no PR, no merge; branch feature/andreaslop-site-hosting pushed (explicit go relayed 2026-11-08).
**AI Response**: Generated operations/monitoring/{monitoring-plan,monitoring-setup}.md. No Sentry alert rules were created (shared project; documented for Bryan/website session). Awaiting approval.
## Operations - Monitoring approval and Production Readiness Validation
**Timestamp**: 2026-11-08
**User Input (via CMS & API)**: Monitoring Setup approved; go to Production Readiness (test only; list production items); do not push doc commits now; Sentry alert rules after the first successful deploy; Bryan starts the CI workflow_dispatch himself.
**AI Response**: No gaps requiring questions. Checklist generated; appsettings compliance passed. Overall Readiness (test): Yes with caveats; 8 open follow-ups. Feature remains open until CI proof and the first test deploy are reported.
@@ -0,0 +1,36 @@
# Production Readiness Checklist - andreaslop-site-hosting
Scope: the TEST environment `test.andreaslop.nl`. Production is out of scope; its open items are only listed at the end.
## Deployment
- **Status**: Configured
- **Method**: CI/CD (Gitea Actions) to the on-premises Pi, test only; switch `ASF_TEST_DEPLOY_ENABLED`
- **Rollback Plan**: Yes (`operations/deployment/rollback-plan.md`: previous release kept, symlink + restart; saved proxy block; CI switch off). Not yet exercised on the Pi.
## Monitoring
- **Status**: Configured (documented; alert rules not yet created)
- **Approach**: Combination: journald + Sentry (website project, environment `test`) with alert rules and an uptime check; no new dashboards
## Additional Readiness Items
- **Backups**: Database `AndreaSlopFotografieTest` must be in the Pi DB backup script (manual step 7, Pi-Main). Status to be confirmed by Pi-Main. The website files live on `/mnt/storage1` and are rebuilt from the website repo. Data Protection keys live in the database.
- **Secrets Management**: Pass. Only in Gitea secrets (`PI_MAIN_*`) and the Pi file `shared/env` (mode 600); `Identity__Setup__Token` is removed after the first administrator exists; nothing secret is committed.
- **Runbook/Support Handover**: Yes. `deployment-instructions.md`, `rollback-plan.md`, `manual-steps-for-bryan.md`, `monitoring-setup.md` are enough for someone other than the author.
- **Alert Ownership**: Bryan receives Sentry e-mail alerts as project owner; fixing is owned by Bryan with the CMS & API and Pi-Main sessions. Rules are created after the first successful deploy.
## .NET Appsettings Compliance
- **Three-file pattern present**: Yes for `Api.AndreaSlopFotografie` (`appsettings.json`, `appsettings.Development.json`, git-ignored optional `appsettings.local.json`, created locally with a placeholder only).
- **No committed secrets**: Pass. `appsettings.json` holds placeholders (`<db-password>`, `<secure-long-random-secret-key-from-env>`), empty token, empty DSN. `appsettings.Development.json` holds the same development-only JWT secret the other clients use and a placeholder database password.
- **`appsettings.local.json` gitignored**: Yes (`.gitignore` line `appsettings.local.json`).
- **Production secrets wired to env vars/secrets manager**: Yes for the test host: `ConnectionStrings__DefaultConnection`, `JwtSettings__Secret`, `Identity__Setup__Token`, `Observability__SentryDsn` via `shared/env`. (Production uses the same mechanism later.)
## Overall Readiness
- **Ready for Production**: Not applicable to production. For TEST: Yes with caveats (below).
- **Open Follow-ups**:
1. CI proof pending: Bryan starts `workflow_dispatch` on the branch (deploy boxes unticked); `backend-test` (MariaDB: `Api.Tests`, ASF `HostPipelineTests`), frontend and vulnerability scan must be green.
2. First test deploy not done (needs the explicit go from CMS & API/Bryan; Pi preparation reported done, proxy route already switched, `ASF_TEST_DEPLOY_ENABLED` unset).
3. After the first deploy: verification list (manual steps 14-18), forwarded-header observation, optional Pi timing, remove the setup token, report in the hand-back.
4. Sentry alert rules to be created after the first successful deploy (by the CMS & API session, with Bryan's go).
5. Backup entry for the test database to be confirmed (Pi-Main).
6. Merging to master deploys the shared Core change and patched packages to SlpSoftware test automatically; watch that deploy.
7. Doc-only commits are local and unpushed.
8. Production for Andrea Slop Fotografie (not prepared, listed only): own database and user, port 5201, own proxy route and certificate, `Website__NoIndex=false`, own `shared/env`, production deploy path/variables and an approval decision, production Sentry environment and alert rules, backup entry, HSTS preload/redirect review, decision on the placeholder radius and dark mode.