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-05-27 11:50:04 +02:00
parent bc8f393f9f
commit 25e15fbeda
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
LNbits-Extensions.md

@ -16,7 +16,7 @@ To make use of all this we introduced a SuperUser, Admin-Users and plain Pleb ac
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 with ```ls -a``` (only ls is not enough to see systemfiles!) then open it with ```sudo nano lnbits.env```or whatever it is called in your implementation.
On Citadel/Umbrel it is called docker-compose.yml.
On Citadel/Umbrel it is called docker-compose.yml. Umbrel has made it available in a special way, try this before messing with CLI if you are not form with it https://apps.umbrel.com/app/lnbits
On MyNode after you activated the Admin-UI (in your case its in /mnt/hdd/mynode/lnbits/) you should be able to see your superuser-id in the logs at this url http://mynode.local/status or find it in your lnbits directory mentioned above. If start up messages have scrolled off, use http://mynode.local/apps and restart LNbits with ```sudo systemctl restart lnbits``` and you should be able to see what's happening in the log.