ci: build-free deploy-services.yml for docs + flatpak server #1
Reference in New Issue
Block a user
Delete Branch "deploy-services-workflow"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds a dispatchable, build-free
deploy-services.ymlsounom/infra'sdeploy-allcan bring a fresh unom-1 fully up in one dispatch — without triggering the heavy builds thatdocker.yml(5-image matrix) andflatpak.yml(full flatpak-builder) run.What it does
scp compose.production.yml→~/punktfunk-docs, thendocker compose pull docs+up -d --no-build(pulls the already-publishedpunktfunk-docs:latest).scp packaging/flatpak/server/{compose.production.yml,Caddyfile}→~/unom-flatpak, thenup -dthecaddy:2-alpinestatic 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) thatdocker.yml/flatpak.ymluse.Not shipped here
The flatpak OSTree content (
./site) is deliberately not part of a deploy — it's regenerated byflatpak.yml's next publish or restored from the unom-1 backup (unom/infra scripts/restore-unom-1.sh,filestag). A fresh box serves an empty repo until then. The stepmkdir -p ~/unom-flatpak/site/repoonly 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 existingsite/(574 M,stable+canaryrefs) untouched.🤖 Generated with Claude Code