Lana (apps VM)
Lana runs the self-hosted apps. Since 2026-11-18 it is a VM on
figgis (VM 101, Ubuntu 26.04, built by the playbook in
docker-infra/ansible), replacing the old Lana VPS.
| Size | 4 vCPU, 16 GiB RAM, 120 GiB disk |
| Network | Private bridge vmbr1, 10.10.10.10; its traffic leaves through figgis’s IP 147.135.38.231. No public ports: the web apps come in through the Cloudflare Tunnel |
| Tailnet | lana, 100.112.192.98, tag:lana |
| SSH | ssh lana (through figgis; the VM firewall only accepts SSH from the host). Git over SSH: lana.taila2470a.ts.net:2222, tailnet only |
Lana is also the Tailscale exit node for your devices (since 2026-11-18): traffic through
it leaves from figgis’s Hillsboro IP 147.135.38.231. The old VPS (66.179.210.123, now
lana-old on the tailnet) still holds stopped copies of everything for rollback.
- Docker Compose for everything, one directory per service, all defined in the
docker-infrarepo, checked out at/opt/docker-infra. Pushing tomaindeploys automatically via Gitea Actions (SSH over Tailscale to100.112.192.98,git pull, decrypt everysecrets.enc.envwith sops, thendocker compose up -dper service). No manual step on the host. - Host setup (sops and its age key, the shared
webandtailscale_tunnelDocker networks, Lana’s own SSH keys, the runner’s deploy key) comes from the playbook’slana_hostanddockerroles. Lana’s outbound keys were made on Lana and never leave it. - Exceptions to the deploy loop: gitea-runner is deployed by hand (recreating it would kill the job running the deploy). Services on Cheryl and Pam have workflows of their own.
- Databases: Postgres 18.7 for Gitea, Authentik and LiteLLM (upgraded from 16 on
2026-11-18 with
scripts/pg-major-upgrade.sh, which dumps, restores into a new volume and compares row counts), MySQL 8.4 for Leantime.
Image versions
Section titled “Image versions”Every image is pinned to an exact version, or to a digest where the running
build has no matching release tag (Open WebUI tracks :main).
Nothing floats on :latest or :main any more.
Upgrades are proposed by the
update-agent,
a scheduled Gitea Actions workflow. It compares each pin against its registry,
has the local Qwen model on Krieger read the release notes in between against the
service’s own compose file, and posts a summary to Discord and Mattermost as the Woodhouse bot.
Updates whose policy is auto and that the model judges safe are applied
straight after the report: database dump, pin bump, deploy, health check, and a
rollback if the service comes up unhealthy. Everything else gets an Apply button
that does the same once you confirm it.
Gitea and its runner are the exception: the updater runs through them, so they
are upgraded by hand.
Other hosts are applied from Lana with DOCKER_HOST (REMOTE in apply.py), the same way
their deploy workflows run: Mattermost and Mumble on ssh://cheryl; arr, Jellyfin and
monitoring on ssh://pam (Lana’s key there may only run sudo docker system dial-stdio, and
Pam’s older Docker needs API 1.43). Garage and forecaster on Pam are refused (ELSEWHERE):
their pins are bumped by hand and pushed.
Tag reading, fixed 2026-10-23: ghcr.io lists tags 1000 at a time, oldest first, and only the
first page used to be read, so images with more tags never saw their newest releases
(LiteLLM sat at v1.91.1 and Gitea at 1.26.4 unnoticed). Every page is read now, with retries
on ghcr’s 429s. linuxserver.io’s -lsN build counter and commit hashes in tags (Plex had them) are
ignored when comparing, because the counter restarts; only a new upstream version is
proposed.
Major-version jumps are never proposed automatically: those are planned
migrations (a Postgres dump/restore, MySQL 8.4 → 26) and are reported separately.
What runs here
Section titled “What runs here”Everything public-facing goes through one of two paths:
- Docker apps behind a Cloudflare Tunnel: Gitea, LiteLLM, Open WebUI,
Leantime, Authentik, knowledge-mcp, and Woodhouse’s sign-in page. No
inbound ports are open for any of these; the
Tunnel connects out to Cloudflare, and
Access gates who can reach most of them.
Also here, tailnet-only: Dozzle (
http://logs/), SearXNG (http://search/; jobs ontailscale_tunnelusehttp://searxng:8080) and LiteLLM’s API on port 4000 for Mattermost’s AI agent on Cheryl. - Static sites via Cloudflare Pages: spelvin.dev itself (this wiki’s landing page) and nothingwilts.com are not Docker containers here at all; they build and deploy straight to Cloudflare Pages from their own Gitea repos via Actions. Lana doesn’t serve their traffic.
Cloudflare Bot Fight Mode is off (since 2026-11-18): it challenged Lana’s own calls to
*.spelvin.dev (the knowledge MCP’s login discovery at Authentik) once Lana’s traffic came from
figgis’s datacenter IP, and on the Free plan no rule can exempt traffic from it.
FlowViz and Windmill were removed on 2026-11-18 (unused). There used to be a legacy path too: a few services sat behind an on-box Caddy + Authelia SSO stack instead of the Tunnel; that’s gone. See Services for the current per-app auth model and what’s been retired along the way (Outline, Plane, n8n, Jupyter, Caddy/Authelia, FlowViz, Windmill).
Full current service list, ports, and auth model: Services.