1.7 KiB
Deployment
HiveGrid Website deploys through Gitea Actions, the Gitea container registry, and Coolify Docker-image resources.
Environments
mainpush stages the current commit tostaging.hivegrid.deon the marketing server through theDeploy stagingworkflow.- The input-free
Promote to productionworkflow resolves the commit and immutable digest currently running on staging and deploys that exact release to the dedicatedhivegrid-prod-websitehost without rebuilding it. - Production serves
hivegrid.deandwww.hivegrid.dethrough 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_IPCOOLIFY_STAGING_API_URLCOOLIFY_STAGING_RESOURCE_UUIDWEBSITE_STAGING_URLCOOLIFY_API_URLCOOLIFY_RESOURCE_UUIDWEBSITE_PRODUCTION_URL
Required repository secrets:
REGISTRY_USERREGISTRY_PATCOOLIFY_STAGING_TOKENCOOLIFY_TOKENCF_ZONE_IDCF_API_TOKEN
Do not commit or paste real Coolify URLs, UUIDs, registry credentials, or Cloudflare tokens into repo files or tickets.