-
Notifications
You must be signed in to change notification settings - Fork 529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CLN] LNBits backed by C-lightning #2556
Comments
Will be do this like with RTL ... having a LNbits & a cLNbits or will this be a selector within the LNbits options/menus somehow? Also we should use this refactor to change the LNbits service to a |
OK ... first I tought lets make two LNbits installations one for lnd and one for c-lightning - like we did for RTL. But came to the conclusion that it just makes sense to have one LNbits installation that takes just one funding source that can be switched. That way even an already running LNbits with accounts is flexible to just change the funding source. Also its easier with all the IP2Tor to just have one instance - thats less confusing. So in general - apps like RTL that are needed to manage a node makes sense to have an instance each for LND & c-lightning. But apps that work on-top and can work with both makes sense to have just one instance and make it easy to switch what node should run in the background. |
OK - ready for testing in branch: https://github.com/rootzoll/raspiblitz/tree/2556cLNbits .. also test recovery for an LNbits switched to cl. To be looked at on a side note:
|
OK merged now into
With
To be restested on a fresh install. |
lnbits switched to fastAPI branch - needs update on commit and restest |
Opened |
OK change to fastAPI seems to work - merging branch into dev for final testing. |
if during the provision the c-lightning was not run yet the lightning-rpc socket does not exist (or might be recreated)
Confirmed:
Solved with :
|
So do I understand that right, that the c-lightning needs to run first (at least once) to create the lightning-rpc socket that lnbits needs on installation? So one solution could be to put the needed configuration into the pre-start script of ln bits? |
Yes, but the limitation of the prestart scripts is that they are running with the unprivileged user (rightly) so cannot modify ownership or user groups. Might be able to make it the part of the c-lightning prestart, will need to check. |
Relaxed the permission of the Also added some debug checks to catch if lnbits is not added to the bitcoin group: 04a3a5a |
do weird.
the checking afterwards:
something must remove it from the |
now it works! |
OK testing looks goog - closing issue for release. |
Hi everyone, |
The configuration changes are simple, but needs testing: https://github.com/lnbits/lnbits/blob/master/docs/guide/wallets.md#clightning
The text was updated successfully, but these errors were encountered: