nickslowinski/vaultwarden-test: Test fork

Test fork

Datei suchen

Jake Howard 743ef74b30 Revert "Add feature to enable use of `Option::or` in const context" This reverts commit `fe8e043b8a`. We want to run on stable soon, where these features are not supported		2022-01-01 23:08:27 +00:00
.github	Optimize release workflow.	2021-09-13 14:42:15 +02:00
docker	Support all DB's for Alpine and Debian	2021-12-26 21:59:28 +01:00
hooks	Support all DB's for Alpine and Debian	2021-12-26 21:59:28 +01:00
migrations	Fix PostgreSQL migration	2021-10-31 17:50:00 -07:00
resources	Storing the original Vaultwarden svg images	2021-07-04 18:37:01 +02:00
src	Revert "Add feature to enable use of `Option::or` in const context"	2022-01-01 23:08:27 +00:00
tools	global_domains.py: allow syncing to a specific Git ref	2021-02-03 12:20:44 -08:00
.dockerignore	Misc changes.	2021-03-30 21:45:10 +02:00
.editorconfig	Misc changes.	2021-03-30 21:45:10 +02:00
.env.template	Better document the new rate limiting	2021-12-25 01:12:09 +01:00
.gitattributes	Just ignore scripts	2021-04-01 20:44:58 +01:00
.gitignore	Rename included .env file to .env.template and ignored .env	2019-01-06 22:50:30 +01:00
.hadolint.yaml	add hadolint config file	2019-07-05 11:06:44 +02:00
.pre-commit-config.yaml	Update some JS Libraries and fix small issues	2021-09-18 19:49:44 +02:00
build.rs	Remove references to "bwrs"	2021-12-31 11:41:34 +00:00
Cargo.lock	Merge branch 'multi-db-dockers' of https://github.com/BlackDex/vaultwarden into BlackDex-multi-db-dockers	2021-12-27 21:55:28 +01:00
Cargo.toml	Merge branch 'multi-db-dockers' of https://github.com/BlackDex/vaultwarden into BlackDex-multi-db-dockers	2021-12-27 21:55:28 +01:00
diesel.toml	Updated dependencies and created 'rust-toolchain', to mark a working nightly to rustup users, and hopefully avoid some nightly breakage.	2018-06-12 17:30:36 +02:00
Dockerfile	Change Dockerfiles to make the AMD image multidb	2020-08-24 20:58:00 +02:00
LICENSE.txt	Upload and download attachments, and added License file	2018-02-15 00:40:34 +01:00
README.md	Update README.md	2021-09-25 13:10:06 +03:00
Rocket.toml	Document configuration a bit and increase JSON size limit to 10MB	2018-06-29 23:11:15 +02:00
rust-toolchain	Support all DB's for Alpine and Debian	2021-12-26 21:59:28 +01:00
rustfmt.toml	Modify rustfmt file	2021-04-06 21:54:42 +01:00
SECURITY.md	Adding a SECURITY.md	2021-06-26 11:49:00 +02:00

README.md

Alternative implementation of the Bitwarden server API written in Rust and compatible with upstream Bitwarden clients*, 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 for more explanation.

Image is based on Rust implementation of Bitwarden API.

This project is not associated with the Bitwarden project nor 8bit Solutions LLC.

⚠️IMPORTANT⚠️: When using this server, please report any bugs or suggestions to us directly (look at the bottom of this page for ways to get in touch), regardless of whatever clients you are using (mobile, desktop, browser...). DO NOT use the official support channels.

Features

Basically full implementation of Bitwarden API is provided including:

Organizations support
Attachments
Vault API support
Serving the static files for Vault interface
Website icons API
Authenticator and U2F support
YubiKey and Duo support

Installation

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

This can be configured in vaultwarden directly or using a third-party reverse proxy (some examples).

If you have an available domain name, you can get HTTPS certificates with Let's Encrypt, or you can generate self-signed certificates with utilities like mkcert. Some proxies automatically do this step, like Caddy (see examples linked above).

Usage

See the vaultwarden wiki for more information on how to configure and run the vaultwarden server.

Get in touch

To ask a question, offer suggestions or new features or to get help configuring or installing the software, please use the forum.

If you spot any bugs or crashes with vaultwarden itself, please create an issue. Make sure there aren't any similar issues open, though!

If you prefer to chat, we're usually hanging around at #vaultwarden:matrix.org room on Matrix. Feel free to join us!