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

Considering a configuration file for protolock #86

Open
sidtaduri opened this issue Jan 8, 2019 · 1 comment
Open

Considering a configuration file for protolock #86

sidtaduri opened this issue Jan 8, 2019 · 1 comment

Comments

@sidtaduri
Copy link

Has a generic configuration file been considered for the tool (in addition to command line args)? It seems like a nice to have, especially for our workflow. We could have a similar setup prior to invoking protolock, but I'm happy to open a PR for a more generic solution if this aligns with the project's goals.

@nilslice
Copy link
Owner

nilslice commented Jan 8, 2019

Hi @sidtaduri - thanks for this proposal. I don't have a strong opinion about the use of a configuration file, but I'd be interested to know what kind of things you'd like to include. It's worth mentioning @btc here, given their recent work on making protolock more configurable as well. @btc, if you have thoughts on this, please feel free to share.

@sidtaduri - if you don't mind, would you post an example configuration file that captures some of your thinking? Thanks!

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

No branches or pull requests

2 participants