unom/punktfunk
1
0
Fork 0
Code Issues Pull Requests Actions 7 Packages Projects Releases 3 Wiki Activity

fix(ci): deploy target is unom-1, not home-main-2
ci / web (push) Failing after 36s
Details
ci / rust (push) Successful in 54s
Details
docker / build-push (., web/Dockerfile, punktfunk-web) (push) Successful in 4s
Details
docker / build-push (ci, ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Successful in 5s
Details
ci / docs-site (push) Failing after 37s
Details
docker / build-push (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Successful in 16s
Details
docker / deploy-docs (push) Successful in 16s
Details
apple / swift (push) Successful in 1m18s
Details

Browse Source 
website/cms deploy to the unom-1 DMZ VM (192.168.50.50) — the
website README's home-main-2 mention is stale. Caddy upstream fixed
in unom/reverse-proxy 6ae79b8, firewall port in unom/infra 9670aa8.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Enrico Bühler
2026-06-12 13:15:16 +00:00
parent 2ed755f0c3
commit 2226031577
3 changed files with 13 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/docker.yml
+4 -3
View File
@@ -60,9 +60,10 @@ jobs:
docker push "$REGISTRY/$OWNER/${{ matrix.image }}:sha-${GITHUB_SHA::8}"
docker push "$REGISTRY/$OWNER/${{ matrix.image }}:latest"
# Deploy the docs site to home-main-2 (docs.punktfunk.unom.io via Caddy on
# home-reverse-proxy-1 -> :3220). Same secret set as unom/website's deploy:
# DEPLOY_HOST/DEPLOY_USER/DEPLOY_PORT/DEPLOY_SSH_KEY (the unom-ci-deploy key).
# Deploy the docs site to unom-1, the DMZ services VM website/cms also deploy to
# (docs.punktfunk.unom.io via Caddy on home-reverse-proxy-1 -> :3220). Same secret set
# as unom/website's deploy: DEPLOY_HOST/DEPLOY_USER/DEPLOY_PORT/DEPLOY_SSH_KEY (the
# unom-ci-deploy key).
deploy-docs:
runs-on: ubuntu-24.04
needs: build-push
compose.production.yml
+2 -2
View File
@@ -1,7 +1,7 @@
# Production compose for the deployed punktfunk pieces — runs on home-main-2 under
# Production compose for the deployed punktfunk pieces — runs on unom-1 (the DMZ services VM, 192.168.50.50) under
# ~/punktfunk-docs (synced there by .gitea/workflows/docker.yml's deploy job; pattern
# follows unom/website + unom/cms). Caddy on home-reverse-proxy-1 serves
# docs.punktfunk.unom.io -> home-main-2:3220 (vhost in unom/reverse-proxy).
# docs.punktfunk.unom.io -> unom-1:3220 (vhost in unom/reverse-proxy).
name: punktfunk-docs-prod
services:
docs:
docs-site/content/docs/ci.md
+7 -6
View File
@@ -58,12 +58,13 @@ ssh enricobuehler@192.168.1.135 GITEA_RUNNER_TOKEN=<token> bash -s \
## Deployment
`docker.yml`'s `deploy-docs` job ships this docs site after every image push: it syncs
`compose.production.yml` to `~/punktfunk-docs` on **home-main-2** and runs
`docker compose pull && up -d` there over SSH (same pattern and secret set as
`unom/website`: `DEPLOY_HOST` / `DEPLOY_USER` / `DEPLOY_PORT` / `DEPLOY_SSH_KEY`, the
`unom-ci-deploy` key). The container binds host port **3220**; Caddy on
`home-reverse-proxy-1` serves it as <https://docs.punktfunk.unom.io> (vhost tracked in
`unom/reverse-proxy`). The host and the web console are NOT deployed — the console
`compose.production.yml` to `~/punktfunk-docs` on **unom-1** (the DMZ services VM
website and cms deploy to) and runs `docker compose pull && up -d` there over SSH (same
pattern and secret set as `unom/website`: `DEPLOY_HOST` / `DEPLOY_USER` / `DEPLOY_PORT` /
`DEPLOY_SSH_KEY`, the `unom-ci-deploy` key). The container binds host port **3220**;
Caddy on `home-reverse-proxy-1` serves it as <https://docs.punktfunk.unom.io> (vhost in
`unom/reverse-proxy`, UniFi firewall allowlist Caddy→unom-1:3220 in `unom/infra`
`proxmox/unom-1`). The host and the web console are NOT deployed — the console
fronts a punktfunk host's management API on whatever box runs the host.
## Troubleshooting