|
|
@@ -1,8 +1,10 @@
|
|
|
### Alternative implementation of the Bitwarden server API written in Rust and compatible with [upstream Bitwarden clients](https://bitwarden.com/#download)*, perfect for self-hosted deployment where running the official resource-heavy service might not be ideal.
|
|
|
|
|
|
+📢 Note: This project was known as Bitwarden_RS and has been renamed to separate itself from the official Bitwarden server in the hopes of avoiding confusion and trademark/branding issues. Please see [#1642](https://github.com/dani-garcia/vaultwarden/discussions/1642) for more explanation.
|
|
|
+
|
|
|
---
|
|
|
|
|
|
-[](https://hub.docker.com/r/vaultwarden/server)
|
|
|
+[](https://hub.docker.com/r/vaultwarden/server)
|
|
|
[](https://deps.rs/repo/github/dani-garcia/vaultwarden)
|
|
|
[](https://github.com/dani-garcia/vaultwarden/releases/latest)
|
|
|
[](https://github.com/dani-garcia/vaultwarden/blob/master/LICENSE.txt)
|
|
|
@@ -35,7 +37,7 @@ Pull the docker image and mount a volume from the host for persistent storage:
|
|
|
docker pull vaultwarden/server:latest
|
|
|
docker run -d --name vaultwarden -v /vw-data/:/data/ -p 80:80 vaultwarden/server:latest
|
|
|
```
|
|
|
-This will preserve any persistent data under /bw-data/, you can adapt the path to whatever suits you.
|
|
|
+This will preserve any persistent data under /vw-data/, you can adapt the path to whatever suits you.
|
|
|
|
|
|
**IMPORTANT**: Some web browsers, like Chrome, disallow the use of Web Crypto APIs in insecure contexts. In this case, you might get an error like `Cannot read property 'importKey'`. To solve this problem, you need to access the web vault from HTTPS.
|
|
|
|