homelab-codex-ws/services/vikunja/docker-compose.yml
Oskar Kapala f7e1391f30 feat(vikunja): bring PIHA Vikunja under GitOps (postgres + Forgejo OIDC)
Wraps the existing manually-run Vikunja instance on PIHA in the standard
service layout. No deploy — definition only, for review.

- services/vikunja/: docker-compose.yml (vikunja + postgres:16-alpine),
  service.yaml, README, healthcheck, config.yml (OIDC, secret-free),
  .env.example. Real .env stays gitignored.
- Pins EXISTING named volumes (vikunja_vikunja_db, vikunja_vikunja_files)
  so DB + uploaded files survive cutover.
- extra_hosts forgejo.okit.pl=192.168.31.5 (npm on PIHA) so OIDC discovery
  resolves over LAN instead of flaky public DNS.
- OIDC client secret injected via env (VIKUNJA_AUTH_OPENID_PROVIDERS_
  FORGEJO_CLIENTSECRET); config.yml keeps trailing-slash authurl/redirecturl.
- Registers vikunja in hosts/piha/services.yaml + inventory/topology.yaml,
  plus hosts/piha/runtime/vikunja override (advisory mem_limits).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-17 15:02:37 +02:00

63 lines
2 KiB
YAML

services:
vikunja:
image: vikunja/vikunja:latest
container_name: vikunja
restart: unless-stopped
depends_on:
db:
condition: service_healthy
# forgejo.okit.pl is pinned to the npm reverse proxy on PIHA so OIDC
# discovery resolves over the LAN instead of flaky public DNS, which was
# causing OIDC discovery to fail.
extra_hosts:
- "forgejo.okit.pl:192.168.31.5"
env_file:
- .env
environment:
- VIKUNJA_DATABASE_TYPE=postgres
- VIKUNJA_DATABASE_HOST=db
- VIKUNJA_DATABASE_PORT=5432
- VIKUNJA_DATABASE_USER=vikunja
- VIKUNJA_DATABASE_DATABASE=vikunja
- VIKUNJA_DATABASE_PASSWORD=${VIKUNJA_DATABASE_PASSWORD:?set in .env}
- VIKUNJA_SERVICE_PUBLICURL=https://vikunja.okit.pl
- VIKUNJA_SERVICE_JWTSECRET=${VIKUNJA_SERVICE_JWTSECRET:?set in .env}
# OIDC client secret injected from .env so config.yml stays secret-free.
- VIKUNJA_AUTH_OPENID_PROVIDERS_FORGEJO_CLIENTSECRET=${VIKUNJA_AUTH_OPENID_PROVIDERS_FORGEJO_CLIENTSECRET:?set in .env}
- TZ=Europe/Warsaw
volumes:
- vikunja_files:/app/vikunja/files
- ./config.yml:/etc/vikunja/config.yml:ro
ports:
- "3456:3456"
healthcheck:
test: ["CMD", "wget", "-qO-", "http://localhost:3456/api/v1/info"]
interval: 30s
timeout: 10s
retries: 5
db:
image: postgres:16-alpine
container_name: vikunja-db
restart: unless-stopped
environment:
- POSTGRES_USER=vikunja
- POSTGRES_DB=vikunja
- POSTGRES_PASSWORD=${POSTGRES_PASSWORD:?set in .env}
- TZ=Europe/Warsaw
volumes:
- vikunja_db:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U vikunja -d vikunja"]
interval: 10s
timeout: 5s
retries: 5
# Pinned to the EXISTING named volumes so the live database and uploaded files
# survive cutover. Do not rename these — the data lives here.
volumes:
vikunja_db:
name: vikunja_vikunja_db
vikunja_files:
name: vikunja_vikunja_files