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
I've written some additional functionality into my fork of fabric-provision to allow for periodic running of chef-solo as well as to support role definitions. Transferring each cookbook and role file over to each remote host on every invocation is somewhat redundant though, so I was wondering what your opinion would be on using fabric.contrib.project.rsync_project() to synchronize the local and remote sets of files. If you're in favor of it, I will go ahead and make the change in my fork, and will send you another pull request for the roles support, the 'runchef' task (to run chef-solo, minus the initial installation), and the rsync file transfer.
The text was updated successfully, but these errors were encountered:
I was actually thinking of adding rsync_project as the preferred way of transferring all the chef files over to a host but just didn't get around to do it. If you do it, I'm very much up for pulling the changes back in.
I've written some additional functionality into my fork of fabric-provision to allow for periodic running of chef-solo as well as to support role definitions. Transferring each cookbook and role file over to each remote host on every invocation is somewhat redundant though, so I was wondering what your opinion would be on using fabric.contrib.project.rsync_project() to synchronize the local and remote sets of files. If you're in favor of it, I will go ahead and make the change in my fork, and will send you another pull request for the roles support, the 'runchef' task (to run chef-solo, minus the initial installation), and the rsync file transfer.
The text was updated successfully, but these errors were encountered: