d-bis/proxmox
4
0
Fork 0
Code Issues 2 Pull Requests 13 Actions Packages Projects Releases Wiki Activity
Files
4c32c0cd60b2e5cb8cc7cec3d1776669737790cf
proxmox/docs/00-meta/GITEA_CD_OPERATOR_CHECKLIST.md
defiQUG bebea622fe
Some checks failed
Deploy to Phoenix / validate (push) Failing after 0s
Details
Deploy to Phoenix / deploy (push) Has been skipped
Details
Deploy to Phoenix / deploy-atomic-swap-dapp (push) Has been skipped
Details
Deploy to Phoenix / cloudflare (push) Has been skipped
Details
feat(gov-portals): Phoenix CD parity, CI templates, sha-on-branch verify 
- Add phoenix-deploy-gov-portal-live-from-workspace.sh (DBIS/ICCC/OMNL/XOM); DBIS script delegates to it.
- deploy-targets: Gov_Web_Portals ICCC/OMNL/XOM with xom-dev healthchecks.
- server.js: optional PHOENIX_DEPLOY_VERIFY_SHA_ON_BRANCH via Gitea commit + compare.
- Gitea workflow templates: dbis/iccc/omnl/xom portal-ci-and-live (monorepo overlay CI, deploy needs verify); concurrency groups; document deploy-only DBIS fallback.
- Docs: GITEA_GOV_PORTALS_LIVE_SOURCE_OF_TRUTH.md; matrix/checklist/AGENTS/MASTER_INDEX/Gov portals deployment cross-links.
- scripts: gitea-tag-repo-release.sh; report-gitea-cd-parity lists repos/*.yml templates.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-12 13:53:10 -07:00

2.0 KiB
Raw Blame History

Gitea CD/CI — operator checklist

Use this after changing phoenix-deploy-api/deploy-targets.json or adding workflows under config/gitea-workflow-templates/.

One-time per application repo (on Gitea)

  1. Actions enabled for the org/repo (Gitea settings).
  2. Secrets on that repo (not only global):
    • PHOENIX_DEPLOY_URL — full URL for POST (same shape as d-bis/proxmox workflows use), typically http://<dev-vm>:4001/api/deploy or HTTPS equivalent.
    • PHOENIX_DEPLOY_TOKEN — bearer token accepted by Phoenix deploy API.
    • GITEA_TOKEN — required for gov portal CI workflows that clone Gov_Web_Portals/gov-portals-monorepo (read-only token is enough).
  3. Workflow file in the repo: copy from config/gitea-workflow-templates/repos/README.md or use the repo’s existing .gitea/workflows/*.yml.

Phoenix deploy host (LAN)

  1. git pull proxmox so deploy-targets.json and scripts/deployment/phoenix-deploy-*.sh match Gitea d-bis/proxmox master / main.
  2. Restart or reinstall phoenix-deploy-api if you manage it via systemd (see phoenix-deploy-api/scripts/install-systemd.sh).
  3. GITEA_TOKEN on that host must allow archive fetch for repos you deploy.
  4. Optional: set PHOENIX_DEPLOY_VERIFY_SHA_ON_BRANCH=1 on the Phoenix deploy API host so POST /api/deploy requests that include sha must resolve to a commit on the declared branch (see phoenix-deploy-api/README.md).

Verify locally (proxmox clone)

bash scripts/validation/validate-phoenix-deploy-targets.sh phoenix-deploy-api/deploy-targets.json
bash scripts/verify/report-gitea-cd-parity.sh

Canonical references

Reference in New Issue View Git Blame Copy Permalink