RWejlgaard/pez-docs
1
0
Fork 0
mirror of https://github.com/RWejlgaard/pez-docs.git synced 2026-05-06 03:34:44 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
pez-docs/workloads/bitwarden/README.md
Rasmus Wejlgaard 4508f740e5 Update documentation for current setup 
- Update locations/london.md with current server state (london-a FreeBSD monitoring, london-b Ubuntu/ZFS storage, london-c offline)
- Update locations/copenhagen.md with current servers (copenhagen-a Minecraft+WoW, copenhagen-b offline, copenhagen-c general)
- Add locations/helsinki.md documenting helsinki-a (Caddy gateway, Authelia, Bitwarden, LDAP) and nuremberg-a (mail/poste.io)
- Add workloads/jellyfin, navidrome, nextcloud, arr-stack, minecraft, wow, mail, monitoring, bitwarden, authelia
- Add principles/zfs documenting the london-b ZFS pool setup
- Add principles/caddy documenting the reverse proxy setup on helsinki-a
- Update introduction.md to mention all locations
2026-03-04 09:41:57 +00:00

566 B
Raw Permalink Blame History

Bitwarden

What

Self-hosted Bitwarden (Vaultwarden) for password management. Running my own instance means my vault never leaves infrastructure I control.

Where

Runs on helsinki-a as a Docker container.

  • URL: bitwarden.pez.sh
  • Backend port: 8443
  • No Authelia — access is controlled by Bitwarden's own auth

Notes

Bitwarden is on helsinki-a rather than london-b because it needs to be highly available. helsinki-a is the public-facing server and has better uptime characteristics than the physical london servers.