Operations: deployment- en monitoringdocumentatie voor andreaslop-site-hosting
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,43 @@
|
||||
# Deployment Setup Plan - andreaslop-site-hosting
|
||||
|
||||
Context: most deployment decisions were already made in U2 Infrastructure Design (CI/CD via Gitea Actions to the test Pi, atomic release switch, rollback by symlink, secrets in `shared/env`, switch variable `ASF_TEST_DEPLOY_ENABLED`). The recommended answers below simply confirm that, so Operations produces one consolidated runbook instead of re-deciding it. Test environment only.
|
||||
|
||||
## Question 1: Include Deployment Setup?
|
||||
Do you want a consolidated deployment runbook and checks for this feature as part of this workflow?
|
||||
|
||||
- A) Yes - consolidate the existing pipeline, the Pi steps and the rollback into one runbook (recommended)
|
||||
- B) No - deployment is handled elsewhere (the infrastructure design and manual steps already cover it)
|
||||
- C) Not sure - suggest an approach and I decide
|
||||
- X) Other (please describe after [Answer]: tag below)
|
||||
|
||||
[Answer]: A (Bryan: "alles A")
|
||||
|
||||
## Question 2: Deployment Method
|
||||
- A) CI/CD pipeline (Gitea Actions, the jobs added in U2) (recommended)
|
||||
- B) Cloud platform
|
||||
- C) On-premises / self-hosted server deployment (done via the pipeline above)
|
||||
- D) Manual deployment
|
||||
- E) Other (please describe after [Answer]: tag below)
|
||||
|
||||
[Answer]: A (Bryan: "alles A")
|
||||
|
||||
## Question 3: Environments
|
||||
- A) Test only (`test.andreaslop.nl`); production is a separate later decision (recommended)
|
||||
- B) Test and production
|
||||
- X) Other (please describe after [Answer]: tag below)
|
||||
|
||||
[Answer]: A (Bryan: "alles A")
|
||||
|
||||
## Question 4: Rollback Strategy
|
||||
- A) Keep the documented approach: previous release stays on disk, `ln -sfn` + restart; route rollback by restoring the saved proxy block; CI off via the switch variable (recommended)
|
||||
- B) Add an automated rollback job to the pipeline
|
||||
- X) Other (please describe after [Answer]: tag below)
|
||||
|
||||
[Answer]: A (Bryan: "alles A")
|
||||
|
||||
## Question 5: Secrets and approval gates
|
||||
- A) Keep: secrets only in Gitea secrets and the Pi `shared/env` (mode 600), no approval gate for test (recommended)
|
||||
- B) Add a manual approval step before the test deploy
|
||||
- X) Other (please describe after [Answer]: tag below)
|
||||
|
||||
[Answer]: A (Bryan: "alles A")
|
||||
@@ -0,0 +1,43 @@
|
||||
# Monitoring Setup Plan - andreaslop-site-hosting
|
||||
|
||||
Context: the CMS already ships structured logging (journald on the Pi), Sentry with alertable security events (`security_event` tag, including the new `setup_token_rejected`), a same-origin `/sentry-tunnel` for the admin, and `/health` (checked by the deploy). The decision (Q3 = B) is to reuse the Andrea Slop Fotografie website's existing Sentry project. Test environment only. Recommended answers are marked.
|
||||
|
||||
## Question 1: Include Monitoring Setup?
|
||||
- A) Yes - document what is observed and add alert recommendations on the existing tooling (recommended)
|
||||
- B) No - reuse the existing setup as is
|
||||
- C) Not sure - suggest an approach
|
||||
- X) Other (please describe after [Answer]: tag below)
|
||||
|
||||
[Answer]: A (Bryan via CMS & API, one by one: all recommended; Q2 = D)
|
||||
|
||||
## Question 2: Monitoring Approach
|
||||
- A) Logging only
|
||||
- B) Alerting only
|
||||
- C) Dashboards only
|
||||
- D) Combination: logging + alerting on existing tooling, no new dashboards (recommended)
|
||||
- E) Other (please describe after [Answer]: tag below)
|
||||
|
||||
[Answer]: A (Bryan via CMS & API, one by one: all recommended; Q2 = D)
|
||||
|
||||
## Question 3: Logging
|
||||
- A) Keep journald on the Pi plus Sentry; `Information` for `SlpModularCms.Website` on test (301/404 lines), `Warning` elsewhere; token never logged (recommended)
|
||||
- B) Add a central log aggregator
|
||||
- X) Other (please describe after [Answer]: tag below)
|
||||
|
||||
[Answer]: A (Bryan via CMS & API, one by one: all recommended; Q2 = D)
|
||||
|
||||
## Question 4: Alerting
|
||||
Which alerts, in the website's Sentry project, notified by email to the project owner?
|
||||
- A) Security events (`setup_token_rejected`, `failed_login`, `rate_limit_triggered`) and any `migration_failure`/unhandled error; plus the website's uptime check on `/health` if Sentry uptime is available (recommended)
|
||||
- B) Only `migration_failure` and unhandled errors
|
||||
- C) No alerts yet
|
||||
- X) Other (please describe after [Answer]: tag below)
|
||||
|
||||
[Answer]: A (Bryan via CMS & API, one by one: all recommended; Q2 = D)
|
||||
|
||||
## Question 5: Dashboards and existing infrastructure
|
||||
- A) No new dashboard; use Sentry issues filtered by environment `test` and the existing Pi tooling (recommended)
|
||||
- B) Add a dedicated dashboard
|
||||
- X) Other (please describe after [Answer]: tag below)
|
||||
|
||||
[Answer]: A (Bryan via CMS & API, one by one: all recommended; Q2 = D)
|
||||
Reference in New Issue
Block a user