dotfiles/roles/vaultwarden/templates/vaultwarden.container

# {{ ansible_managed }}

[Unit]
Description=Vaultwarden
After=postgresql.service
Requires=postgresql.service

[Container]
ContainerName=vaultwarden
Image=ghcr.io/dani-garcia/vaultwarden:latest
AutoUpdate=registry

EnvironmentFile=/etc/vaultwarden.ini

Network=vaultwarden.network
PublishPort={{ vaultwarden_http_port }}:80
PublishPort=3012:3012

Volume=vaultwarden-data:/data

[Service]
Restart=always

[Install]
WantedBy=multi-user.target
style: add Ansible-managed headers Signed-off-by: Matej Focko <me@mfocko.xyz> 2024-11-15 16:50:11 +01:00			`# {{ ansible_managed }}`

feat(vaultwarden): deploy from quadlet Related to #51 Signed-off-by: Matej Focko <me@mfocko.xyz> 2024-11-14 16:50:43 +01:00			`[Unit]`
			`Description=Vaultwarden`
fix: require postgresql for forgejo and vaultwarden Storing data for Forgejo and Vaultwarden in the postgres database results in a rather wonky behavior during restarts of the VPS and potential restarts of the postgres itself. Based on some observations Forgejo is capable of recovering from such issues, but Vaultwarden falls into a retry loop trying to reconnect to the database while failing on resolving the hostname / connecting, e.g., [2024-11-27 16:52:43.646][r2d2][ERROR] connection to server at "host.containers.internal" (XXX.XXX.XXX.XXX), port 5432 failed: Connection refused Therefore adjust the quadlet definitions to require and boot containers »after« the postgres is running to minimalize the possible issues. Signed-off-by: Matej Focko <me@mfocko.xyz> 2024-11-27 17:57:35 +01:00			`After=postgresql.service`
			`Requires=postgresql.service`
feat(vaultwarden): deploy from quadlet Related to #51 Signed-off-by: Matej Focko <me@mfocko.xyz> 2024-11-14 16:50:43 +01:00
			`[Container]`
			`ContainerName=vaultwarden`
			`Image=ghcr.io/dani-garcia/vaultwarden:latest`
feat(quadlets): allow auto-update by podman Signed-off-by: Matej Focko <me@mfocko.xyz> 2024-11-18 15:48:02 +01:00			`AutoUpdate=registry`
feat(vaultwarden): deploy from quadlet Related to #51 Signed-off-by: Matej Focko <me@mfocko.xyz> 2024-11-14 16:50:43 +01:00
			`EnvironmentFile=/etc/vaultwarden.ini`

			`Network=vaultwarden.network`
fix(vaultwarden): handle reverse proxy Signed-off-by: Matej Focko <me@mfocko.xyz> 2024-11-18 15:47:36 +01:00			`PublishPort={{ vaultwarden_http_port }}:80`
feat(vaultwarden): deploy from quadlet Related to #51 Signed-off-by: Matej Focko <me@mfocko.xyz> 2024-11-14 16:50:43 +01:00			`PublishPort=3012:3012`

			`Volume=vaultwarden-data:/data`

			`[Service]`
			`Restart=always`

			`[Install]`
			`WantedBy=multi-user.target`