lnbits deployment seems to work
This commit is contained in:
parent
a41e1d9383
commit
0db4cf94b5
4 changed files with 249 additions and 1 deletions
|
|
@ -142,3 +142,34 @@ ntfy is a notifications server.
|
|||
### Backups
|
||||
|
||||
Given that ntfy is almost stateless, no backups are made. If it blows up, simply set it up again.
|
||||
|
||||
|
||||
## LNBits
|
||||
|
||||
LNBits is a Lightning Network wallet and accounts system.
|
||||
|
||||
### Deploy
|
||||
|
||||
* Decide what subdomain you want to serve LNBits on and add it to `services/lnbits/lnbits_vars.yml` on the `lnbits_subdomain`.
|
||||
* Note that you will have to add a DNS entry to point to the VPS public IP.
|
||||
* Run the deployment playbook: `ansible-playbook -i inventory.ini services/lnbits/deploy_lnbits_playbook.yml`.
|
||||
|
||||
### Configure
|
||||
|
||||
* LNBits will be available for you to create a superuser on first start. Do that and store the creds safely.
|
||||
* From that point on, you can configure through the Web UI.
|
||||
* Some advice around specifics of LNbits:
|
||||
* The default setup uses a FakeWallet backend for testing. Configure a real Lightning backend as needed by modifying the `.env` file located or using the superuser UI.
|
||||
* For security, disable the new users registration.
|
||||
|
||||
### Set up backups to Lapy
|
||||
|
||||
* Make sure rsync is available on the host and on Lapy.
|
||||
* Run the backup playbook: `ansible-playbook -i inventory.ini services/lnbits/setup_backup_lnbits_to_lapy.yml`.
|
||||
* A first backup process gets executed and then a cronjob is set up to refresh backups periodically. The script backs up both the `.env` file and the sqlite database. Backups are gpg encrypted for safety.
|
||||
|
||||
### Restoring to a previous state
|
||||
|
||||
* Stop LNBits.
|
||||
* Overwrite the data folder with one of the backups.
|
||||
* Start it up again.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue