I run on a cheap cloud vps to get a static IP, use Caddy to connect it to a domain, and then connect to a different funding source not on that vps. Takes only a few minutes to set up the LNbits side of it. If your funding source is behind tor then you’d have to either setup tor on the LNbits server or a vpn. I just use a custodial backend because mine is only for small amounts, hobby use, anyway.
This section of the LNbits documentation talks about connecting to various funding sources.
Keeping LNbits separate from your funding node makes it all much more flexible and probably safer too.
https://github.com/lnbits/lnbits/wiki/LNbits-Documentation#funding-sources
Indeed this is a good scenario, easy to switch anytime to multiple funding sources.
Even if you use a temporary custodial funding source (let's say you don't have your own LN node available) like LNpay or lntipbot, you can always use the Scrub LNbits extension and forward automatically all sats to any other own destination wallet.
LNbits is a really powerful tool, endless ln address, endless lnurls, endless ln-auth, and many cool things, including the new Market extension.
