ci: build-free deploy-services.yml for docs + flatpak server #1

2026-07-10T19:14:46Z

enricobuehler commented

2026-07-10 19:14:46 +00:00

Adds a dispatchable, build-free deploy-services.yml so unom/infra's deploy-all can bring a fresh unom-1 fully up in one dispatch — without triggering the heavy builds that docker.yml (5-image matrix) and flatpak.yml (full flatpak-builder) run.

What it does

docs — scp compose.production.yml → ~/punktfunk-docs, then docker compose pull docs + up -d --no-build (pulls the already-published punktfunk-docs:latest).
flatpak — scp packaging/flatpak/server/{compose.production.yml,Caddyfile} → ~/unom-flatpak, then up -d the caddy:2-alpine static server.

Reuses the exact deploy artifacts already in this repo (no vendored copies) and the same SHA-pinned appleboy actions + secret set (DEPLOY_*, REGISTRY_TOKEN) that docker.yml/flatpak.yml use.

Not shipped here

The flatpak OSTree content (./site) is deliberately not part of a deploy — it's regenerated by flatpak.yml's next publish or restored from the unom-1 backup (unom/infra scripts/restore-unom-1.sh, files tag). A fresh box serves an empty repo until then. The step mkdir -p ~/unom-flatpak/site/repo only ensures the bind-mount source exists.

Verified

Dispatched on this branch against the live box: both jobs green; docs :3220→200, flatpak :3230→200; the existing site/ (574 M, stable + canary refs) untouched.

🤖 Generated with Claude Code

Adds a dispatchable, **build-free** `deploy-services.yml` so `unom/infra`'s `deploy-all` can bring a fresh unom-1 fully up in one dispatch — without triggering the heavy builds that `docker.yml` (5-image matrix) and `flatpak.yml` (full flatpak-builder) run. ## What it does - **docs** — `scp compose.production.yml` → `~/punktfunk-docs`, then `docker compose pull docs` + `up -d --no-build` (pulls the already-published `punktfunk-docs:latest`). - **flatpak** — `scp packaging/flatpak/server/{compose.production.yml,Caddyfile}` → `~/unom-flatpak`, then `up -d` the `caddy:2-alpine` static server. Reuses the exact deploy artifacts already in this repo (no vendored copies) and the same SHA-pinned appleboy actions + secret set (`DEPLOY_*`, `REGISTRY_TOKEN`) that `docker.yml`/`flatpak.yml` use. ## Not shipped here The flatpak OSTree **content** (`./site`) is deliberately not part of a deploy — it's regenerated by `flatpak.yml`'s next publish or restored from the unom-1 backup (`unom/infra scripts/restore-unom-1.sh`, `files` tag). A fresh box serves an empty repo until then. The step `mkdir -p ~/unom-flatpak/site/repo` only ensures the bind-mount source exists. ## Verified Dispatched on this branch against the live box: both jobs green; `docs :3220`→200, `flatpak :3230`→200; the existing `site/` (574 M, `stable` + `canary` refs) untouched. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

enricobuehler added 2 commits 2026-07-10 19:14:47 +00:00

ci: deploy-only workflow for docs + flatpak server (no rebuild) 124a81e861

docker.yml (5-image matrix) and flatpak.yml (full flatpak-builder) couple the
docs + flatpak-server deploys to heavy builds. This adds a dispatchable,
build-free deploy-services.yml that just (re)places the compose files and pulls
the already-published images, so unom/infra's deploy-all can bring a fresh
unom-1 fully up in one dispatch. The flatpak ./site OSTree content is restored
from the unom-1 backup or regenerated by flatpak.yml's next publish.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

ci: fix deploy-services.yml content (was double-encoded)

ci / web (pull_request) Successful in 51s

Details

ci / docs-site (pull_request) Successful in 1m6s

Details

apple / swift (pull_request) Successful in 4m31s

Details

apple / screenshots (pull_request) Has been skipped

Details

ci / bench (pull_request) Successful in 6m36s

Details

android / android (pull_request) Successful in 11m4s