update vaultwarden docs
This commit is contained in:
parent
14075fe1cc
commit
2097a39663
1 changed files with 12 additions and 5 deletions
|
|
@ -48,6 +48,7 @@ Uptime Kuma gets used to monitor the availability of services, keep track of the
|
||||||
### Deploy
|
### Deploy
|
||||||
|
|
||||||
* Decide what subdomain you want to serve Uptime Kuma on and add it to `services/uptime_kuma/uptime_kuma_vars.yml` on the `uptime_kuma_subdomain`.
|
* Decide what subdomain you want to serve Uptime Kuma on and add it to `services/uptime_kuma/uptime_kuma_vars.yml` on the `uptime_kuma_subdomain`.
|
||||||
|
* Note that you will have to add a DNS entry to point to the VPS public IP.
|
||||||
* Make sure docker is available on the host.
|
* Make sure docker is available on the host.
|
||||||
* Run the deployment playbook: `ansible-playbook -i inventory.ini services/uptime_kuma/deploy_uptime_kuma_playbook.yml`.
|
* Run the deployment playbook: `ansible-playbook -i inventory.ini services/uptime_kuma/deploy_uptime_kuma_playbook.yml`.
|
||||||
|
|
||||||
|
|
@ -76,20 +77,26 @@ Vaultwarden is a credentials manager.
|
||||||
### Deploy
|
### Deploy
|
||||||
|
|
||||||
* Decide what subdomain you want to serve Vaultwarden on and add it to `services/vaultwarden/vaultwarden_vars.yml` on the `vaultwarden_subdomain`.
|
* Decide what subdomain you want to serve Vaultwarden on and add it to `services/vaultwarden/vaultwarden_vars.yml` on the `vaultwarden_subdomain`.
|
||||||
|
* Note that you will have to add a DNS entry to point to the VPS public IP.
|
||||||
* Make sure docker is available on the host.
|
* Make sure docker is available on the host.
|
||||||
* Run the deployment playbook: `ansible-playbook -i inventory.ini services/vaultwarden/deploy_vaultwarden_playbook.yml`.
|
* Run the deployment playbook: `ansible-playbook -i inventory.ini services/vaultwarden/deploy_vaultwarden_playbook.yml`.
|
||||||
|
|
||||||
|
### Configure
|
||||||
|
|
||||||
|
* Vaultwarden will be available for you to create a user on first start. Do that and store the creds safely.
|
||||||
|
* From that point on, you can configure through the Web UI.
|
||||||
|
|
||||||
|
### Disable registration
|
||||||
|
|
||||||
|
* You probably don't want anyone to just be able to register without permission.
|
||||||
|
* To prevent that, you can run the playbook `disable_vaultwarden_sign_ups_playbook.yml` after creating the first user.
|
||||||
|
|
||||||
### Set up backups to Lapy
|
### Set up backups to Lapy
|
||||||
|
|
||||||
* Make sure rsync is available on the host and on Lapy.
|
* Make sure rsync is available on the host and on Lapy.
|
||||||
* Run the backup playbook: `ansible-playbook -i inventory.ini services/vaultwarden/setup_backup_vaultwarden_to_lapy.yml`.
|
* Run the backup playbook: `ansible-playbook -i inventory.ini services/vaultwarden/setup_backup_vaultwarden_to_lapy.yml`.
|
||||||
* A first backup process gets executed and then a cronjob is set up to refresh backups periodically.
|
* A first backup process gets executed and then a cronjob is set up to refresh backups periodically.
|
||||||
|
|
||||||
### Configure
|
|
||||||
|
|
||||||
* Vaultwarden will be available for you to create a user on first start. Do that and store the creds safe.
|
|
||||||
* From that point on, you can configure through the Web UI.
|
|
||||||
|
|
||||||
### Restoring to a previous state
|
### Restoring to a previous state
|
||||||
|
|
||||||
* Stop Vaultwarden.
|
* Stop Vaultwarden.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue