Just run your own self-custodial cloud Lightning node on your VPS, from your domain name, with this stack. You immediately get a LNBits instance on your own node and the phoenixd endpoint available on a SSL connection.
A multistack feature has been added and makes possible to add multiple stacks to the same VPS, served simultaneously.
cd ~
git clone https://github.com/massmux/lightstack.git
cd lightstack
choose two subdomains on your domain, where you have the DNS management. They must point the A record to the host server IP and this must be already propagated when you are going to invoke initialization script. In my example they are
- n1.yourdomain.com
- lb1.yourdomain.com
n1 will be the endpoint for phoenixd APIs lb1 will be the lnbits install
cd lightstack
./init.sh
The interactive init script makes possible to choose beween using PostgreSQL or SQLite as database support, and choose self-signed certificates (for testing purposes) or Letsencrypt ones. You will be asked during install.
PostgreSQL is better when thinking to large amount of users installs.
In case you need to start inizialization from the beginning, you need to clear existing configuration (if the case) by issuing:
./init.sh clear
Please note that this will clear all data, configuration files and database in existing directory. If you had funds in that node, you will loose them all, so be careful and check it before
Help shows usage and active stacks. Stacks can be also removed by the below commands:
dev@lightstack:~/lightstack$ sudo ./init.sh help
You have the following active stacks:
ID PHOENIXD LNBITS
1 n1.yourdomain.com lb1.yourdomain.com
2 n2.yourdomain.com lb2.yourdomain.com
Usage: init.sh [command]
command:
add [DEFAULT]: to init a new system and/or add a new stack
clear: to remove all stacks
del|rem: to remove a stack
help: to show this message
Access LNBITS instance at:
Access phoenixd API endpoint with:
- https://n1.yourdomain.com
- http password: provided in phoenix.conf file
in case you want to tune your configuration you can always setup the .env file as you prefer.