homelab-codex-ws/kb/services/vikunja.md
oskar a1a57b04bb feat(kb): przenosiny type=service do kb/services/ (13 plikow, bez SPLIT)
Serwisy o jednorodnej tresci (bez wydzielonej sekcji deploy/runbook):
kb-postgres, stability-agent, llm-gateway, vikunja, zigbee2mqtt, npm,
forgejo, ollama, ir-ac-ha-integration, chelsty-stability-agent.

Deprecated: mosquitto (NOT DEPLOYED/LEGACY), home-assistant-ken-legacy
(archiwum importu), joplin (stub z 2026-04-15, brak katalogu services/joplin/).

git mv + frontmatter, tresc nietknieta.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-04 16:58:04 +02:00

1.9 KiB

okf type visibility status updated links
0.1 service private active 2026-06-17

Vikunja

Self-hosted task management. Runs on the PIHA node with a dedicated PostgreSQL backend, exposed publicly at https://vikunja.okit.pl via the npm reverse proxy on PIHA. Login is via Forgejo OIDC.

Stack

Container Image Purpose
vikunja vikunja/vikunja:latest App + API (port 3456)
vikunja-db postgres:16-alpine PostgreSQL (service alias db)

Data (do not move)

Persistent state lives in pre-existing Docker named volumes — these are pinned by name so the live data survives cutover:

  • vikunja_vikunja_db/var/lib/postgresql/data
  • vikunja_vikunja_files/app/vikunja/files

Configuration

  • config.yml — committed, secret-free. Holds OIDC provider metadata.
  • .envgitignored. Copy from env.example and fill with the real live values (must be identical to the running instance):
    • POSTGRES_PASSWORD / VIKUNJA_DATABASE_PASSWORD (same value)
    • VIKUNJA_SERVICE_JWTSECRET
    • VIKUNJA_AUTH_OPENID_PROVIDERS_FORGEJO_CLIENTSECRET

Notes

  • forgejo.okit.pl is pinned via extra_hosts to 192.168.31.5 (npm on PIHA) so OIDC discovery resolves over the LAN, avoiding flaky public DNS.
  • Both redirecturl and the provider authurl MUST keep their trailing slash — the authurl must match the OIDC issuer exactly or discovery fails.

Cutover checklist

  1. git pull on PIHA.
  2. Create services/vikunja/.env from env.example with the real values.
  3. Confirm the named volumes exist: docker volume ls | grep vikunja_vikunja.
  4. docker compose -f services/vikunja/docker-compose.yml up -d.
  5. Verify: ./healthcheck.sh and a test OIDC login.