Closed ale-rinaldi closed 3 years ago
thanks!
ok, if you care about user accounts, then yes, redis database backup is a must. if not - all fund are still in LND, so you only need lnd's mnemonic seed and channels backup (which is basically ~/.lnd
folder)
what are BLW using for its backend to their build version of LndHub ?
is it postgress
interesting - echo chamber here hello hello
silence
interesting - echo chamber here hello hello
silence
The lndhub repo is open and anyone can see it. It is written there.
Not sure why someone should invest their time replying to this
what are BLW using for its backend to their build version of LndHub ?
is it postgress
or You only run with redis ?
i am adding a adapter to LndHub that can have several stores as connectors to the adapter
Redis Sqlite3 Postgress Mongo MySql
"Not sure why someone should invest their time replying to this"
and I am not sure i PR here . just fork seems more sane
thanks
Only runs with Redis.
so to make it clear BlueWallet's default LN backend only runs on Redis ?
so to make it clear BlueWallet's default LN backend only runs on Redis ?
I'm not understanding where is the doubt. Yes, Redis.
i imagine you have a lot of tx passing through so the accounting and reporting stats helpdesk etc. would be more flexible with a db made for such requests with joins ++
so i was curious se what You use as backend for BlueWallet users there and if You have a special build with added functionality
lndhub is the backend for lighning for bluewallet. there is nothing else
Hello,
I managed to install my own LndHub instance on a Debian server. What should back up to be able to restore the exact situation if the server catches fire?
From LND I'm backing up the entire .lnd folder on a regular basis.
What about LndHub? Should I back up the Redis instance? I also suggest to mention this in the documentation, I think it's a must-have information.
Thanks for your great work!