Skip to content
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

Override defaults #108

Closed
kevintraver opened this issue Jan 18, 2016 · 3 comments
Closed

Override defaults #108

kevintraver opened this issue Jan 18, 2016 · 3 comments

Comments

@kevintraver
Copy link

It would be nice override defaults in a config file. Maybe something like ~/.rtail

@kilianc
Copy link
Owner

kilianc commented Jan 18, 2016

Hey @kevintraver thanks for stopping by.

In particular are you referring to the server or the client ? I have thought about this in the past but people seem to be very opinionated about file naming, location, format etc...

I would more likely add a --config-file using the config module on npm which will give us OOTB support for yml, json, hjson etc

I see no harm in having --config-file in both server and client.

Not sure yet what the behavior should be for mixed args+file options, I think args should always override the config file.

PR is welcome.

@kbariotis
Copy link

@kilianc the config module expects to find the configuration files inside the root of the project. But many people will install rtail globally. Having a ~/.rtail config file seems more appropriate.

This was referenced Mar 19, 2016
@kevintraver
Copy link
Author

Fixed in #113

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants