Closed aupiff closed 6 years ago
Allowing the location of the config file to be provided via CLI argument to the lndr cli tool and the lndr-backend server would be nice. Something like --config-file <path>
and/or -f <path>
. I'm totally up to update the deployment tooling to drop the config wherever.
atomically
atomically
when it is not strictly necessary (it is only necessary when reading an updating aTVar
must be done atomically; this happens inupdateConfig
during the heartbeat or duringfinalizeTransaction
which updates the execution nonce)scanblockchain
&consistencycheck
CLI actions to replace /unsubmittedloadConfig
to accept a filepath parameterWhat a successful consistency check looks like now:
NOTE: CLI now expects a
lndr-server.config
in the home directory. I'd changelndr-backend
to require the same instead of using the relative pathlndr-backend/data/lndr-server.config
but I don't want to mess with @canterberry's deployments.