From 1a881525496bf62a802882b4eab89c84fa5fed04 Mon Sep 17 00:00:00 2001
From: arbadacarba <63317640+arbadacarbaYK@users.noreply.github.com>
Date: Thu, 20 Apr 2023 20:31:32 +0200
Subject: [PATCH] Updated LNbits Extensions (markdown)

---
 LNbits-Extensions.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/LNbits-Extensions.md b/LNbits-Extensions.md
index 780417d..05f1131 100644
--- a/LNbits-Extensions.md
+++ b/LNbits-Extensions.md
@@ -14,7 +14,9 @@ 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 on by extending the command to list files in your directory to  ```ls -a```. 
+
 On Citadel/Umbrel it is called docker-compose.yml. 
+
 On MyNode you should be able to see it in  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.
 
 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.