bugclerk dce032f49b Upgraded catalog item(s) (#2125) 1 éve
..
charts 05b43f54d6 bump common (#2059) 1 éve
ci f3cd41e787 remove immutable flag from hostPath (#1858) 1 éve
migrations 6c35baa25c vaultwarden - migrate storage section (#1766) 1 éve
templates b3f86c948f fix(vaultwarden): pass ixChartContext to postgres template (#1991) 1 éve
Chart.lock 05b43f54d6 bump common (#2059) 1 éve
Chart.yaml dce032f49b Upgraded catalog item(s) (#2125) 1 éve
README.md 846a6a02c4 NAS-121156 / 23.10 / Add vaultwarden to community train (#1055) 2 éve
app-readme.md 846a6a02c4 NAS-121156 / 23.10 / Add vaultwarden to community train (#1055) 2 éve
item.yaml 40fe463839 Update screenshot/icon links to ix CDN (#1646) 1 éve
metadata.yaml 31962e8241 NAS-121769 / 23.10 / Add metadata file(s) (#1175) 2 éve
questions.yaml f3cd41e787 remove immutable flag from hostPath (#1858) 1 éve
upgrade_info.json 846a6a02c4 NAS-121156 / 23.10 / Add vaultwarden to community train (#1055) 2 éve
upgrade_strategy 193fc134db fix typo in update_strategy (#1083) 2 éve
values.yaml dce032f49b Upgraded catalog item(s) (#2125) 1 éve

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).