Commit graph

3 commits

Author SHA1 Message Date
Maximilian Grimm
d5398caece Episode 4: Vaultwarden single sign-on via Forgejo
- compose: SSO_ENABLED, SSO_AUTHORITY and the two client credentials, with the
  undocumented redirect path written down where people will look for it
- .env.example: was referenced by the README since episode 1 but never actually
  committed, so a fresh clone could not follow the quickstart
- README: the four steps, plus the debugging notes that cost the most time
  (no SSO line at startup, 404 on routes without query parameters, HEAD on the
  discovery endpoint, and the three-step member join)
- HARDENING: never copy db.sqlite3 alone while the container runs. WAL mode
  keeps recent writes in a side file, so that backup silently misses data
2026-08-26 21:54:23 +02:00
Maximilian Grimm
0341ae777d Episode 2: Forgejo Actions — runner, Docker sandbox, own registry, locked-down deploy 2026-08-19 22:21:20 +02:00
Maximilian Grimm
06f8e8812e Initial stack: Caddy, Forgejo, Outline, Vaultwarden, Uptime Kuma, n8n 2026-08-16 19:29:58 +02:00