|
|
9 mesiacov pred | |
|---|---|---|
| .. | ||
| charts | 1 rok pred | |
| ci | 2 rokov pred | |
| migrations | 2 rokov pred | |
| templates | 1 rok pred | |
| Chart.lock | 1 rok pred | |
| Chart.yaml | 9 mesiacov pred | |
| README.md | 2 rokov pred | |
| app-readme.md | 2 rokov pred | |
| item.yaml | 2 rokov pred | |
| metadata.yaml | 2 rokov pred | |
| questions.yaml | 2 rokov pred | |
| upgrade_info.json | 2 rokov pred | |
| upgrade_strategy | 2 rokov pred | |
| values.yaml | 9 mesiacov pred | |
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).