Open ghost opened 8 years ago
In fact "config-local" can be located anywhere. It can be specified with the "--config-local" parameter.
ma-image-resize-tool --config config.json --config-local config-local.json
Though, the path is relative to the current working directory, not "config.json"'s location.
Most of the time I want to edit the
config-local.json
file but have to traverse deep down to the image-tool location (_stuff\source\
in our case). It would be nice if theconfig-local.json
could be located in a different location than theconfig.json
and instead refer to it via a parameter but still use theconfig.json's
location as the "working directory".