1 Introduction
Previously, Vaultwarden (originally called Bitwarden_RS) was used to implement a personal password manager. If it is used by a team, unit or even an enterprise, a more professional Bitwarden is needed.
Reference article:
Docker website building (6) Vaultwarden: a secure and private personal password manager
https://blog.tsinbei.com/archives/731/
But I found that many functions are not very easy to use. After some searching, I found out that Vaultwarden is an unofficial project, and only part of the functions have been implemented.
So, I found this official project on GitHub: Bitwarden.
2. Installation
Bitwarden officially provides a one-click installation script:
Comment first then view it after your comment is approved. Join QQ Group to display all hidden texts.
Next the script will ask for the initial configuration:
1 | Enter the domain name for your Bitwarden instance # Enter the domain name you want to assign to Bitwarden, the example here is bw.tsinbei.com Do you want to use Let’s Encrypt to generate a free SSL certificate? (y/n) # Whether to use Let's Encrypt to automatically generate a free SSL certificate, generally select y (you can also select n if you have your own certificate, and you need to configure the path of the certificate later) # Use the inverse method of the second article in this series, then choose n Enter the database name for your Bitwarden instance # Enter the database name for Bitwarden, fill in whatever you want Enter your installation id / Enter your installation key # Visit https://bitwarden.com/host to get a set of installation ID and installation key Key, free of charge |
Once everything is set up, the installation is complete.
On the Docker manager page, you can see several more containers, corresponding to Bitwarden's password manager, enterprise single sign-on SSO server, API server, etc.
3. Configuration
The configuration file is in the installation directory
/bwdata/env/global.override.env
Check the comments and add them yourself, so I won't repeat them here.
All commands supported by ./bitwarden.sh
:
command | description |
---|---|
install | Start the installer |
start | Start all containers |
restart | Restarts all containers (same as start) |
stop | Stop all containers |
update | Update Bitwarden version |
updatedb | update/initialize database |
updateself | updates the bitwarden.sh file itself |
updateconf | Updates all containers without restarting running instances |
renewcert | Renew Certificate |
rebuild | Rebuild configuration in config.yml |
help | list all commands |
For example, to modify the above configuration file, you need to execute:
1 | ./bitwarden.sh rebuild ./bitwarden.sh restart |
4. Use
Refer to Vaultwarden, Vaultwarden is perfectly compatible with Bitwarden, so the usage method will not be repeated here.
Note: Bitwarden takes up a lot of space. Personal use is a waste of server resources. If there is no team of more than 20 people, it is recommended to use Vaultwarden.
5. Summary
At present, Bitwarden is not as good as other similar paid software in terms of appearance and user experience, but Bitwarden is free and open source, and supports privatized deployment. It also has considerable advantages.
Most importantly, Bitwarden supports seamless import of 1Password data, which is indeed a pretty good free alternative to 1Password.
Finally, the same sentence:
Privacy should be in your own hands.
Docker Website (9) BitWarden
Comments