all-in-one/community-containers/vaultwarden/readme.md

Vaultwarden

This container bundles vaultwarden and auto-configures it for you.

Notes

• You need to configure a reverse proxy in order to run this container since vaultwarden needs a dedicated (sub)domain! For that, you might have a look at https://github.com/nextcloud/all-in-one/tree/main/community-containers/caddy or follow https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md and https://github.com/dani-garcia/vaultwarden/wiki/Proxy-examples
• Currently, only bw.$NC_DOMAIN is supported as subdomain! So if Nextcloud is using your-domain.com, vaultwarden will use bw.your-domain.com. The reverse proxy and domain must be configured accordingly!
• If you want to secure the installation with fail2ban, you might want to check out https://github.com/nextcloud/all-in-one/tree/main/community-containers/fail2ban
• The data of Vaultwarden will be automatically included in AIOs backup solution!
• After adding and starting the container, you need to visit https://bw.your-domain.com/admin in order to log in with the admin key that you can retrieve when running sudo docker inspect nextcloud-aio-vaultwarden | grep ADMIN_TOKEN. There you can configure smtp first and then invite users via mail. After this is done, you might disable the admin panel via the reverse proxy by blocking connections to the subdirectory.
• See https://github.com/nextcloud/all-in-one/tree/main/community-containers how to add it to the AIO stack

Repository

https://github.com/dani-garcia/vaultwarden

Maintainer

https://github.com/szaimen