Add GHCR-backed Portainer activation path #35

Merged

florianbeisel merged 4 commits from clawteam/rauchbar-dev/deploy-platform into main

2026-03-26 11:36:13 +01:00

florianbeisel commented

2026-03-26 11:28:21 +01:00

(Migrated from github.com)

Summary

switch the Portainer deployment path to prebuilt GHCR image references instead of Git-based compose builds
add GHCR publish workflow, image-aware prework validation, and updated Portainer stack/env/runbook docs
keep provider API keys optional while real-send flags remain disabled

Verification

render-stack-env.sh renders GHCR_NAMESPACE and IMAGE_TAG successfully
docker compose --env-file /tmp/stack-ghcr.env -f docker-compose.portainer.yml config passes
workflow YAML parses for portainer-stack-ci, portainer-deploy-prework, and portainer-image-publish

## Summary - switch the Portainer deployment path to prebuilt GHCR image references instead of Git-based compose builds - add GHCR publish workflow, image-aware prework validation, and updated Portainer stack/env/runbook docs - keep provider API keys optional while real-send flags remain disabled ## Verification - render-stack-env.sh renders GHCR_NAMESPACE and IMAGE_TAG successfully - docker compose --env-file /tmp/stack-ghcr.env -f docker-compose.portainer.yml config passes - workflow YAML parses for portainer-stack-ci, portainer-deploy-prework, and portainer-image-publish

florianbeisel commented

2026-03-26 11:29:14 +01:00

(Migrated from github.com)

Blocking issue: GitHub currently reports this PR as CONFLICTING / DIRTY against main, so it is not merge-ready yet. The new GHCR-backed Portainer path looks coherent at the file level, and both current checks are green, but the branch still needs a refresh/rebase onto latest main before it can be reviewed clear for landing.

florianbeisel commented

2026-03-26 11:36:01 +01:00

(Migrated from github.com)

Re-review at d05889e: no blocking findings. The earlier conflict-only blocker is resolved and GitHub now shows the branch as mergeable again. The diff remains limited to the GHCR-backed Portainer activation path, and a local verification pass succeeded for docker compose --env-file /tmp/rauchbar-pr35/ops/portainer/stack.env.example -f /tmp/rauchbar-pr35/docker-compose.portainer.yml config plus ops/portainer/render-stack-env.sh --check with the required GHCR/image-tag variables populated.

Re-review at d05889e: no blocking findings. The earlier conflict-only blocker is resolved and GitHub now shows the branch as mergeable again. The diff remains limited to the GHCR-backed Portainer activation path, and a local verification pass succeeded for docker compose --env-file /tmp/rauchbar-pr35/ops/portainer/stack.env.example -f /tmp/rauchbar-pr35/docker-compose.portainer.yml config plus ops/portainer/render-stack-env.sh --check with the required GHCR/image-tag variables populated.