-
Notifications
You must be signed in to change notification settings - Fork 11
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
BTCPay Server on LunaNode with no Bitcoin node #9
Comments
The launchbtcpay.lunanode.com creates VM with btcpayserver-docker which I believe is designed to work with internal Lightning node (Lightning runs in one of the Docker containers it creates). You should be able to configure BTCPay to use existing Lightning node, but in this case you may have to install it manually rather than create it from the launcher. In this case it is possible that the 1 GB RAM in m.1s plan is enough. |
On a LunaNode instance of BTC Pay server, I did try changing out the lightning node and that worked fine. I'll have to give manual installation a try. It would be great at some point to have the m.1s plan as an option through the launcher only if none of the 'supported cryptocurrencies' were checked. Maybe with a message warning that selecting m.1s would mean an external lightning node would be needed. |
In this case you can try the guide at https://medium.com/@BtcpayServer/hosting-btcpayserver-on-lunanode-bf9ef5fff75b |
Jumping here: Do not deploy BTCPay Server with an external node. (external lightning is OK) |
Would it be possible to get the LunaNode VM Plan down to m.1s instead of m.2 if one just wanted to spin up an instance of BTCPay Server, but use an existing lightning node (not hosted on LunaNode)? The goal being to get the convenience of having a pubic facing IP address generated (instead of using something like the IP2TOR tunnel service), a quickly generated hostname, a valid HTTPS certificate instead of a self-signed HTTPS certificate that would give security warnings, and less down-time potentially than a self-hosted instance.
It seems removing the initial syncing of any blockchain, not having to store the large file size of the Bitcoin blockchain, and not having the extra traffic of the constant saving of new blocks should allow the LunaNode VM requirements to drop, yet m.2 is the cheapest plan that can be selected via launchbtcpay.lunanode.com.
The text was updated successfully, but these errors were encountered: