Posted by bryan kennedy on April 14, 2013 at 6:19pm
Hey Folks,
I've been working on some deploy recipes for Drupal, built upon the great Python tool Fabric. Drush still does most of the heavy lifting, but Fabirc gives me a nice way of putting a several commands together into a single deploy or development workflow command.
I'm packaging these recipes together in a set of modules called Neoprene. It's pretty alpha code at this stage but someone on another group suggested some folks in this channel might find this useful.
https://github.com/scimusmn/neoprene
Check it out, fork, and submit pull-requests if there's anything you see you could improve.
Comments
It would be great if there
It would be great if there was some example documentation/usage of this.
Yeah some usage examples may
Yeah some usage examples may help explain the 'why'. Right now it seems that just using drush and site aliases would accomplish the same thing.
I agree
I only glanced over the scripts, but my first thought was "why not just use drush". Personally, I wrap drush scripts in Fabric for certaim situations like deployment.
Great suggestion. I'll try to
Great suggestion. I'll try to expose stuff like this usage example...
https://github.com/scimusmn/neoprene/blob/master/init.py#L128
...at a higher level as things get developed out.
404 on that link you posted
404 on that link you posted above.
Have you used site aliases before? The allow you to use drush against any Drupal install running on any server, which seems to be the functionality you want.
http://drush.ws/examples/example.aliases.drushrc.php