Closed ross-spencer closed 2 years ago
Thinking about it this morning, rather than creating something like a /home/user/.demystify
we can use getpwd
to identify if there is a config file there. Then make sure we point clearly to the template configuration files in the root dir of the repo. That means we don't have to create too much excess on anyone's machines for a feature they may not use. The idea can be evolved if need be.
Denylist is hard-coded for demystify-lite: https://github.com/exponential-decay/demystify/commit/0b709605872836356eb6d05b76c92a95e4a086c5#diff-59a2a915e109873a5708ba9c19d31fd57e3931b55cc2196cd5b16fe7c33077c7R99
Handled here: https://github.com/exponential-decay/demystify/pull/81/commits/7e4d63f77ab74a4268ac288cc83bb50e890de07d
The script requires a denylist.cfg
file in the current working directory. A baseline template can be output with --denylist_template
.
As per above, and included in: https://github.com/exponential-decay/demystify/commit/aafc72481b7d7276eac043fe7501fa3267c37c80
As we package demystify, config at the root folder level begins to not make sense. Config needs to be done elsewhere, e.g. within a user's home folder.
Connected to #48