(Abondoned) Add lnbits

[petzsch]

THIS PR is ABONDONED and will be closed in 1 month!
More details see the last post on the PR.

⚠️This pull request is a work in progress.
⚠️Warning: There are still many moving parts in this PR, test at your own risk and please don't use for production setups!
⚠️Warning: Switching to this branch, will update your setup to BTCPay Server 2.0

If you want to support the testing of this PR, you can check it out following:

1. cd /root/BTCPayServer/btcpayserver-docker/ (or where you orginallly checked out the btcpayserver-docker repo)
2. git remote set-url origin https://github.com/petzsch/btcpayserver-docker.git
3. git pull
4. git checkout add-lnbits
5. follow the docs: here.

TODOs:

• fix the retry issue (will be fixed in 0.12.8 docker image)
• create lnbits-configure.sh script (move env vars in docker file, create config wizard etc.)
• more testing
• mergen branch test-lnbits-0.12.8 into this one
• C-Lightning switched to clightning-rpc for 0.1.2.8 until lnbits supports CLNRest: Add support for the new CLNRest as a funding source so that runes can be used to give LNBits limited access to the lightning node lnbits/lnbits#2232
• figure out the implications of not having AUTH_SECRET_KEY configured or howto do it the proper way
• make it run on minmial installs without LND and CLN / remove this line

[PatMulligan]

add after line 171?
* [opt-add-lnbits](docker-compose-generator/docker-fragments/opt-add-lnbits.yml), for a self-hosted lnbits backed by BTCPay Server.

[petzsch]

add after line 171? * [opt-add-lnbits](docker-compose-generator/docker-fragments/opt-add-lnbits.yml), for a self-hosted lnbits backed by BTCPay Server.

Thanks for pointing this out. I've added your suggestion.

[Meisterzunge]

When does this feature will be approved? Cant wait for it 🙃

[Meisterzunge]

The custom fragment works well!

Hint:
If you set the LNBITS_ALLOWED_USERS variable to your admin user ID, other users won't be able to login to your lnbits instance. You should remove this line from the sample fragment wich will be part of the documentation. Or add a proper comment to it.

[petzsch]

Please note: I've merged the 2.0 branch into this PR's branch. This means when you run an btcpay-update.sh you will get the new 2.0 Release.

Please read this for understanding breaking changes: https://blog.btcpayserver.org/btcpay-server-2-0/

[petzsch]

This fragment is abandoned!

Here the instructions to remove it from your BTCPay Setup. Remember to also remove it from your Store settings, if you used the lndhub interface.

1. export LNBITS_HOST="(empty)"
2. check your current fragment list with: printenv | grep -i additional_fragments

the output could look something like this:

BTCPAYGEN_ADDITIONAL_FRAGMENTS=opt-save-storage-s;opt-add-lnbits;opt-add-lnbits-admin.custom

remove the lnbits related fragments from the list and re-export the variable:

export BTCPAYGEN_ADDITIONAL_FRAGMENTS="opt-save-storage-s"

3. cd /root/BTCPayServer/btcpayserver-docker
4. git remote set-url origin https://github.com/btcpayserver/btcpayserver-docker.git
5. git pull
6. git checkout 2.0
7. . btcpay-setup.sh -i
8. btcpay-update.sh

There will be no future updates from my end. This PR will be closed 2nd Jan 2025.

Alternatives

For Boltcard functionality checkout @NicolasDorier 's plugin.

For hosting Lnbits you can checkout their SaaS service.