-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support project-wide configuration #5
Comments
I think it fits. About the name i guess .config.nuwk would be more obvious. |
So be it. |
node-runtime-configuration seems to handle the job quiet well, with environment and command lime overloading if necessary. It will look at |
Hi @mackwic, any new from the owner? |
Yep, he’s waiting for my pull request, which is on its way. It will probably be ok wednesday. -- De: Alessandro Benoit [email protected] Hi @mackwic, any new from the owner? — |
Cool! 2014-07-07 15:34 GMT+02:00 Thomas Wickham [email protected]:
Alessandro Benoit |
I am still uncertain about the greatest name convention for this (maybe throw it in the package.json ? But which one ?)
Anyway, we need a project-wide configuration. Defaults will be the one shipped with the application, and each value will be overridable.
Proposals for the local config file:
.nuwk
.config.nuwk
Sparse config file are bad. It clutters the file tree with thing we never edit again.
I am all for checking first the dedicated config file, then check for the
nuwk
key in the package.json, then apply defaults.What do you think of that ?
The text was updated successfully, but these errors were encountered: