there are independent services, including the ui, each offering a set of options controllable by user. for example, bitcoin-core and lnd settings.
users must be able to tweak settings from the touchscreen. how to propagate these to the services? one way is for nd to receive commands from ngui and change the corresponding file(s) like bitcoind.conf or lnd.conf.
another idea is to have a global settings storage from which to (re)generate those corresponding config files or cmd flags. this feels like a more robust approach, unifying different configuration styles into a service-agnostic system.
now, how to store these global settings. sqlite or a text file?
there are independent services, including the ui, each offering a set of options controllable by user. for example, bitcoin-core and lnd settings.
users must be able to tweak settings from the touchscreen. how to propagate these to the services? one way is for `nd` to receive commands from `ngui` and change the corresponding file(s) like bitcoind.conf or lnd.conf.
another idea is to have a global settings storage from which to (re)generate those corresponding config files or cmd flags. this feels like a more robust approach, unifying different configuration styles into a service-agnostic system.
now, how to store these global settings. sqlite or a text file?
x1ddos
added this to the mvp v1.0 milestone 2 years ago
there are independent services, including the ui, each offering a set of options controllable by user. for example, bitcoin-core and lnd settings.
users must be able to tweak settings from the touchscreen. how to propagate these to the services? one way is for
ndto receive commands fromnguiand change the corresponding file(s) like bitcoind.conf or lnd.conf.another idea is to have a global settings storage from which to (re)generate those corresponding config files or cmd flags. this feels like a more robust approach, unifying different configuration styles into a service-agnostic system.
now, how to store these global settings. sqlite or a text file?