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

fix(ci): deploy target is unom-1, not home-main-2

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 eecb1583c9
commit 027d6bc7c7
3 changed files with 13 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
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: