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

Best practices? Config file organization? #1905

Open
alexander233 opened this issue Nov 23, 2018 · 1 comment
Open

Best practices? Config file organization? #1905

alexander233 opened this issue Nov 23, 2018 · 1 comment

Comments

@alexander233
Copy link

Are there any hints to best practices about how to organize administrative tasks and config files with Fabric 2 - e.g. if I have multiple servers against which I want to run commands?
Fabric 2 looks very good but it would be easier if some examples as to how one might set up a config file with information about a few servers and how a few tasks would be organized in a useful way.
I understand that Fabric does not want to be normative there, but examples on how some of you set this up would be helpful.

@JamesRamm
Copy link

I would also be interested in best practices with regards to configuration, especially for larger projects where you might want to share default values among mulitple tasks, but still allow them to be overridden on the command line...

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