You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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...
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.
The text was updated successfully, but these errors were encountered: