4 ms·
That's a silly reason. At simplest, you could a) log the entire config at startup. or b) create a specific file with config used, if logging is too messy.
by silisili 4y ago
That's a silly reason. At simplest, you could
a) log the entire config at startup.
or
b) create a specific file with config used, if logging is too messy.
or
c) make an API to return the running config.
or
d) use envvars in a container, that you can just dump from 'env' at will.
All of which would be cleaner and saner than browsing top.