[GitHub] ctubbsii commented on issue #188: Use conf/uno-local.conf if it exists

[GitBox <gi...@apache.org>]

ctubbsii commented on issue #188: Use conf/uno-local.conf if it exists
URL: https://github.com/apache/fluo-uno/pull/188#issuecomment-413026702
 
 
   For these kinds of things, I think a better pattern is: source the global/default env, then source user-specific overrides.
   
   So, what we should do is source `conf/uno.conf`, and follow that with `~/.config/uno.conf` (or `~/.unorc` or similar). That way, users can override, but don't have to maintain any synchronicity with the default `uno.conf` file when it gets updates.
   
   This pattern is so ubiquitous, I'm not sure it makes sense to invent our own pattern with an alternate `-local` construct.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services