Files

2.1 KiB

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)

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)

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)

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)

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)