enricobuehler
f47f7989e0
The unom tenant's footer doc has no sections yet (the multi-tenant migration backfilled the old footer to the punktfunk tenant), so the footer rendered as an empty, near-invisible bar. Render a sensible default (Übersicht/Rechtliches links + site tagline) when there are no CMS sections; CMS content overrides it once the unom footer is populated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@unom/website
The unom.io marketing site. TanStack Start + Bun, deployed to home-main-2.
Development
bun install
bun run dev
Visit http://localhost:3000.
Production
The repo is built into a container image (git.unom.io/unom/website) by Gitea
Actions on push to main, then deployed via SSH to home-main-2. The
container listens on port 3000 inside the network and is exposed on host port
3200, which Caddy on home-reverse-proxy-1 reverse-proxies for unom.io and
www.unom.io.
Run the production image locally:
docker compose -f compose.production.yml pull
docker compose -f compose.production.yml up -d
Required CI secrets
Set on the unom/website repo in Gitea Actions:
| Secret | Purpose |
|---|---|
REGISTRY_USER / REGISTRY_TOKEN |
Push to git.unom.io container registry |
DEPLOY_HOST / DEPLOY_USER / DEPLOY_PORT / DEPLOY_SSH_KEY |
SSH target on home-main-2 (private key matching the unom-ci-deploy authorized key) |