highperfocused/lnbits
1
0
Fork 0
mirror of https://github.com/lnbits/lnbits.git synced 2025-03-27 02:02:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated LNbits Extensions (markdown)

arbadacarba 2023-04-21 00:38:07 +02:00
parent 65eb1baa2c
commit faec4b1195
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
LNbits-Extensions.md

@ -13,11 +13,11 @@ Please note that any other extension you find on the wild west of the internet m
## Install Extensions
The LNbits Admin UI lets you change LNbits settings via the LNbits frontend. It is disabled by default and the first time you set the enviroment variable LNBITS_ADMIN_UI=true in the .env the settings are initialized and saved to the database and will be used (as long the UI is enabled). You will find the .env file within your lnbits/ or lnbits/apps/data folder by extending the command to list files in your directory to ```ls -a```.
The LNbits Admin UI lets you change LNbits settings via the LNbits frontend. It is disabled by default and the first time you set the enviroment variable LNBITS_ADMIN_UI=true in the .env the settings are initialized and saved to the database and will be used (as long the UI is enabled). You will find the .env file within your lnbits/ or lnbits/apps/data folder by extending the command to list files in your directory to ```ls -a``` then open it with sudo nano lnbits.env
On Citadel/Umbrel it is called docker-compose.yml.
On MyNode you should be able to see your superuser-id in the logs at this url http://mynode.local/status. If start up messages have scrolled off, use http://mynode.local/apps and Restart LNbits and you should be able to see what's happening in the log.
On MyNode after you activated the Admin-UI you should be able to see your superuser-id in the logs at this url http://mynode.local/status or find it in you lnbits directory as mentioned above. If start up messages have scrolled off, use http://mynode.local/apps and restart LNbits and you should be able to see what's happening in the log.
From there on the settings from the database instead those of the .env file are used. If you want to return to those settings you can just set LNBITS_ADMIN_UI=false and restart LNbits to take the .env again.
On restart of LNbits you will find the link to the superuser-AdminUI in your terminal. Save if good and never share it.