johnheenan
johnheenan
> Alternatively a separate flag for lnd, btcpay restart. > > Eg. `--include-lnd-graph` (default no) `--restart` (default yes) Everything restarts except LND if full LND backup is taken. Once LND...
Also what about this addiitonal flag for restore? `--reenable-lnd` Reenable LND if it was disabled With this flag for backup? `--disable-lnd` Disable lnd if enabled and exit without further action
> Also what about this addiitonal flag for restore? > > `--reenable-lnd` Reenable LND if it was disabled > > With this flag for backup? `--disable-lnd` Disable lnd if enabled...
> --no-restart > [prevents btcpay-up from running after backup complete] If will put that in but I will still to disable LND. Meaning that if there is a subsequebt restart...
Changes made as per request. Easiest way to view entire changes is from https://github.com/btcpayserver/btcpayserver-docker/pull/928/files
> Looks already very good 👏 I agree with @damanic that `export BTCPAYGEN_LIGHTNING="none"` probably is a bad idea. I think if `export BTCPAYGEN_LIGHTNING="none"` is removed then their should only be...
If someone If someone is going to migrate lnd, shouldn't they know the consequences of messing it up by restarting without lnd disabled? However, who reads command output and warnings?...
If someone leaves btcpay down on old server then there are no problems. It is common practice with web migration to restart old servers with a maintenace page showing. The...
> IMO warning and no restart should suffice for the backup script. OK, changes made. Dire warnings show up if 1. LND is currently enabled 2. `include-lnd-graph` is included 3....
I am in no way advocating any weakening of card security. My point has not been understood. I will try and explain it better. **I believe there should be four...