In #1504598: Discuss merging Vagrant-based Drupal/Drush projects, I suggest merging various efforts around integrating Vagrant and Drupal/Drush. I'd like to invite you to take part in that discussion.

Comments

Steven Merrill’s picture

Steven Merrill commented

All right - I'll join in pretty soon.

The one thing I like best about drush-vagrant is that it can be installed in a single drush command ("drush dl drush-vagrant"), so as long as we maintain that, I am all about consolidation. :)

Steven Merrill’s picture

Steven Merrill commented

We talked briefly in #drupal-nyc about this today. I'd be cool with combining all the Vagrant-related Drush commands into the drush-vagrant project (in a 2.0 branch.) The current drush-vagrant command could be renamed to drush vagrant-alias and then the aegir-up commands added.

Steven Merrill’s picture

Steven Merrill commented

Ergonlogic is now a maintainer of drush-vagrant, so let the consolidation commence!

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented

Steven was nice enough to grant me commit access, so I'll start moving stuff over to a 2.x from aegir-up.

patcon’s picture

patcon commented

LOVE this discussion!

Been working with Vagrant (and Chef) for about a year, and haven't been vocal enough until recently.

Just to toss out what I think would be a holy grail in terms of creating a vagrant setup for using vagrant as a dev tool:

vagrant drupal-up --patch=http://drupal.org/node/1317054#comment-5848278

And with that:

  • arse the page DOM for the:
    1. patch url,
    2. post date, and
    3. module

      4. ,

  • match the date to the git commit (perhaps several, working back until success)
  • parse module .info file for deps and download them
  • run site-install

Bam. One command from the issue queues, and anyone is set up to test a patch, with barely any effort or even understanding as to how it all happening (for better or for worse).

Perhaps a bit outside the scope of discussion, but do you guys think it's a grail worth pursuing? I mean, I'm sure we might find this stuff simple, but it was a good 18 months before I applied my first patch back in the ol' days, and one command is pretty tempting :)

patcon’s picture

patcon commented

Oh hey, and obviously, since we're all in lurve with drush, that command should totally be resurfaced as a drush command

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented
Version: 7.x-1.0-alpha3 » 7.x-2.x-dev
Component: Miscellaneous » Code
Assigned: Unassigned » ergonlogic

I've merged the git history of Aegir-up into the 7.x-2.x branch, and integrated just about everything. I've split out each of the command callbacks into it's own include file, along with one for all helper functions that aren't specific to such a command callback, since it was getting a little unwieldy.

I need to finish splitting out the new framework (mostly just Puppet Fact injection), then rework some of the blueprints a bit to work with it. These blueprint will then get split back off to their own projects, but I'd like to build at least one default/example blueprint to include within drush-vagrant by default. To that end, I've posted #1536800: Default blueprint.

Also, I build my base boxes on Debian, and have included Veewee definitions for them. Not sure where they should go.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented
Status: Active » Fixed

I'd say this is pretty much complete, and with the upcoming addition of #1532506: Drush aliases for VMs, I think it'll be worthy of a (beta) release.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.