Oskar Kapala
f7e1391f30
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>
12 lines
310 B
YAML
12 lines
310 B
YAML
# PIHA-specific overrides for Vikunja.
|
|
#
|
|
# PIHA is not as RAM-constrained as the VPS, so these limits are advisory
|
|
# guard-rails (a leaking process gets restarted by Docker) rather than a hard
|
|
# budget. Adjust if Vikunja's working set grows.
|
|
services:
|
|
vikunja:
|
|
mem_limit: 768m
|
|
|
|
db:
|
|
mem_limit: 256m
|