55 lines
1.7 KiB
Markdown
55 lines
1.7 KiB
Markdown
# Deployment
|
|
|
|
HiveGrid Website deploys through Gitea Actions, the Gitea container registry,
|
|
and Coolify Docker-image resources.
|
|
|
|
## Environments
|
|
|
|
- `main` push stages the current commit to `staging.hivegrid.de` on the
|
|
marketing server through the `Deploy staging` workflow.
|
|
- The input-free `Promote to production` workflow resolves the commit and
|
|
immutable digest currently running on staging and deploys that exact release
|
|
to the dedicated `hivegrid-prod-website` host without rebuilding it.
|
|
- Production serves `hivegrid.de` and `www.hivegrid.de` through the HiveGrid
|
|
production Coolify instance.
|
|
|
|
## Image Tags
|
|
|
|
The staging workflow publishes the immutable full commit SHA and updates the
|
|
mutable `staging` alias. Promote reads the short revision from the live staging
|
|
health endpoint, resolves it to exactly one commit on `main`, verifies that its
|
|
image digest matches both the registry alias and the Coolify staging resource,
|
|
then updates the `main` production alias without rebuilding.
|
|
|
|
The previous production digest is captured automatically in the workflow
|
|
summary as the rollback reference.
|
|
|
|
## Promote to Production
|
|
|
|
Open **Actions → Promote to production → Run workflow** and run it from
|
|
`main`. There are no SHA or confirmation inputs.
|
|
|
|
## Gitea Configuration
|
|
|
|
Required repository variables:
|
|
|
|
- `HIVEGRID_GITEA_HOST_IP`
|
|
- `COOLIFY_STAGING_API_URL`
|
|
- `COOLIFY_STAGING_RESOURCE_UUID`
|
|
- `WEBSITE_STAGING_URL`
|
|
- `COOLIFY_API_URL`
|
|
- `COOLIFY_RESOURCE_UUID`
|
|
- `WEBSITE_PRODUCTION_URL`
|
|
|
|
Required repository secrets:
|
|
|
|
- `REGISTRY_USER`
|
|
- `REGISTRY_PAT`
|
|
- `COOLIFY_STAGING_TOKEN`
|
|
- `COOLIFY_TOKEN`
|
|
- `CF_ZONE_ID`
|
|
- `CF_API_TOKEN`
|
|
|
|
Do not commit or paste real Coolify URLs, UUIDs, registry credentials, or
|
|
Cloudflare tokens into repo files or tickets.
|