From e0b19ecb869fa2def96127a970c57755897cc1d9 Mon Sep 17 00:00:00 2001
From: arbadacarba <63317640+arbadacarbaYK@users.noreply.github.com>
Date: Mon, 8 May 2023 14:17:30 +0200
Subject: [PATCH] Updated LNbits Extensions (markdown)

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

diff --git a/LNbits-Extensions.md b/LNbits-Extensions.md
index 08a0798..ef1d17e 100644
--- a/LNbits-Extensions.md
+++ b/LNbits-Extensions.md
@@ -23,6 +23,7 @@ On MyNode after you activated the Admin-UI you should be able to see your superu
 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.
 See [this guide to become admin and define who is allowed to add which extensions](https://gist.github.com/callebtc/61417cce47ff00a8ed4d19c45f1ff10f). Demo video on [how to install and activate a new extension](https://www.youtube.com/watch?v=98VYC99s770) or [read here](https://github.com/lnbits/lnbits/blob/main/docs/guide/extension-install.md#install-new-extension).
+Within the manifest you can also define correlations of those extensions in the new field "dependencies".
 When the AdminUI is opened we can move on. 
 
 **Please be aware that in some cases making use of the new features could mean that the QR of existing QR Codes will change (e.g. in LNURLdevices, LNURLp that especially is the case).**