|
%!s(int64=2) %!d(string=hai) anos | |
---|---|---|
.. | ||
charts | %!s(int64=2) %!d(string=hai) anos | |
ci | %!s(int64=2) %!d(string=hai) anos | |
migrations | %!s(int64=2) %!d(string=hai) anos | |
templates | %!s(int64=2) %!d(string=hai) anos | |
Chart.lock | %!s(int64=2) %!d(string=hai) anos | |
Chart.yaml | %!s(int64=2) %!d(string=hai) anos | |
README.md | %!s(int64=2) %!d(string=hai) anos | |
app-readme.md | %!s(int64=2) %!d(string=hai) anos | |
item.yaml | %!s(int64=2) %!d(string=hai) anos | |
metadata.yaml | %!s(int64=2) %!d(string=hai) anos | |
questions.yaml | %!s(int64=2) %!d(string=hai) anos | |
upgrade_info.json | %!s(int64=2) %!d(string=hai) anos | |
upgrade_strategy | %!s(int64=2) %!d(string=hai) anos | |
values.yaml | %!s(int64=2) %!d(string=hai) anos |
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
Vaultwarden
data directory. Afterward, theVaultwarden
container will run as a non-root user (default568
). Same applies to thepostgres
container. 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 thepostgres
backups 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:999
on every update. But will only be changed once for theVaultwarden
andpostgres
data 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).