mirror of
https://github.com/lnbits/lnbits.git
synced 2025-03-27 02:02:14 +01:00
Updated LNbits Extensions (markdown)
parent
b840020868
commit
ecc31e1b3d
@ -5,12 +5,11 @@
|
||||
|
||||
Installable Extensions and their decentralization came to life thanks to incredible [motorina0](https://github.com/motorina0).
|
||||
Like WordPress, we will maintain a vetted collection of extensions, but each user is also free to install existing 3rd party ones - and to [create own LNbits extensions](https://github.com/lnbits/lnbits/wiki/LNbits-Documentation#developing-with-lnbits). The extension manifest is on a public repo anyone can submit to.
|
||||
Each extension is from now on pulled from its own repo when you install them explicitely (rather than all being packaged into LNbits core), for a slim and more secure LNbits 💪🚀 [All vetted extensions](https://github.com/lnbits/lnbits-extensions) are verified by a hash checksum 🍻
|
||||
Each extension is from now on pulled from its own repo when you install them explicitely (rather than all being packaged into LNbits core), for a slim and more secure LNbits. [All vetted extensions](https://github.com/lnbits/lnbits-extensions) are verified by a hash checksum.
|
||||
|
||||
Please note that any other extension you find on the wild west of the internet might not only not work but could also include malicious content as well. Dont trust - verify! Please report to the [LNbits Telegram Group](https://t.me/lnbits) if you experience smth suspicious.
|
||||
|
||||
To make use of all this we introduced a SuperUser, Admin-Users and plain Pleb accounts. We made a whole [chapter about the differences here](https://github.com/lnbits/lnbits/wiki/LNbits-Documentation#additional-guides). For those that like to activate them manually via CLI/Terminal this might be enough. All others please come back here once you understood those differences and you are ready to take off.
|
||||
Please note, that any other extension you find on the wild west of the internet might not only not work but could also include malicious content as well. Dont trust - verify! Please report to the [LNbits Telegram Group](https://t.me/lnbits) if you experience smth suspicious.
|
||||
|
||||
To understand the differences between the SuperUser, Admin-Users and plain Pleb accounts we made a whole [chapter about them here](https://github.com/lnbits/lnbits/wiki/LNbits-Documentation#additional-guides).
|
||||
***
|
||||
|
||||
|
||||
@ -30,10 +29,10 @@ On Start9 go to Properties, and open the Superuser URL from there.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
From there on the settings from the database instead those of the .env file are used.
|
||||
On restart of LNbits you will find a new file named ".super_user" containing the superuser-ID in the lnbits folder. 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".
|
||||
Within the manifest you can also define correlations of those extensions with the parameter "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).**
|
||||
@ -57,7 +56,7 @@ As an admin you only have available what the superuser installed and allowed you
|
||||
|
||||
Now that the extensions are taken out of core LNbits we can also update each extension separately!
|
||||
|
||||
- Open your LNbits instance as super admin (not as a regular user. You will find the SuperUser-ID in your server logs on restart of LNbits. Use that to bookmark and manage LNbits from there in the future.)
|
||||
- Open your LNbits instance as super admin (not as a regular user.
|
||||
Now lets install the new version of a given extension like extensively [described in the guide already linked above for installation](https://github.com/lnbits/lnbits/blob/main/docs/guide/extension-install.md#install-new-extension). In short:
|
||||
- Go to "Mange extensions", click on "ALL", search for the one you want to update, e.g. LNURLp, click on "Manage"
|
||||
- Open the details of the extension and click on the version you need, click "Install". You´re done!
|
||||
|
Loading…
x
Reference in New Issue
Block a user