846a6a02c4
* Add vaultwarden to community train * add variable only when set * Update library/ix-dev/community/vaultwarden/values.yaml * Update library/ix-dev/community/vaultwarden/values.yaml * add NET_BIND_SERVICE * minor typo * use the new common * Update common * add upgrade_info.json * remove the capability, and bump to fixed version
1.3 KiB
Vaultwarden
Vaultwarden Alternative implementation of the Bitwarden server API written in Rust and compatible with upstream Bitwarden clients
During the installation process, a container will be launched with root privileges. This is required in order to apply the correct permissions to the
Vaultwardendata directory. Afterward, theVaultwardencontainer will run as a non-root user (default568). Same applies to thepostgrescontainer. This will run afterwards as a non-root user (999). On each upgrade, a container will be launched with root privileges in order to apply the correct permissions to thepostgresbackups directory. Container that performs the backup will run as a non-root user (999) afterwards. Keep in mind the permissions on the backup directory will be changed to999:999on every update. But will only be changed once for theVaultwardenandpostgresdata directories.
While the option to use Rocket for TLS is there, it is not
recommended.
Instead, use a reverse proxy to handle TLS termination.
Using HTTPS is required for the most of the features to work (correctly).