Stavros Kois 85d2fab14d NAS-122030 / 23.10 / Adds check to only render hostPath key if it has a value (#1210) 2 lat temu
..
charts 9d4c420c86 NAS-121780 / 23.10 / Add tags to apps (#1193) 2 lat temu
ci 846a6a02c4 NAS-121156 / 23.10 / Add vaultwarden to community train (#1055) 2 lat temu
migrations 85d2fab14d NAS-122030 / 23.10 / Adds check to only render hostPath key if it has a value (#1210) 2 lat temu
templates 9d4c420c86 NAS-121780 / 23.10 / Add tags to apps (#1193) 2 lat temu
Chart.lock 9d4c420c86 NAS-121780 / 23.10 / Add tags to apps (#1193) 2 lat temu
Chart.yaml 85d2fab14d NAS-122030 / 23.10 / Adds check to only render hostPath key if it has a value (#1210) 2 lat temu
README.md 846a6a02c4 NAS-121156 / 23.10 / Add vaultwarden to community train (#1055) 2 lat temu
app-readme.md 846a6a02c4 NAS-121156 / 23.10 / Add vaultwarden to community train (#1055) 2 lat temu
item.yaml bd7bdb4e2f NAS-121977 / 23.10 / Add screeshots to apps (#1215) 2 lat temu
metadata.yaml 31962e8241 NAS-121769 / 23.10 / Add metadata file(s) (#1175) 2 lat temu
questions.yaml db5e1a9b69 Remove 20 char limit for the vaultwarden admin token (#1189) 2 lat temu
upgrade_info.json 846a6a02c4 NAS-121156 / 23.10 / Add vaultwarden to community train (#1055) 2 lat temu
upgrade_strategy 193fc134db fix typo in update_strategy (#1083) 2 lat temu
values.yaml 85d2fab14d NAS-122030 / 23.10 / Adds check to only render hostPath key if it has a value (#1210) 2 lat temu

README.md

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 Vaultwarden data directory. Afterward, the Vaultwarden container will run as a non-root user (default 568). Same applies to the postgres 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 the postgres 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 to 999:999 on every update. But will only be changed once for the Vaultwarden and postgres 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).