Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.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
Comment #1
Steven Merrill CreditAttribution: Steven Merrill commentedAll 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. :)
Comment #2
Steven Merrill CreditAttribution: Steven Merrill commentedWe 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-vagrantcommand could be renamed todrush vagrant-aliasand then the aegir-up commands added.Comment #3
Steven Merrill CreditAttribution: Steven Merrill commentedErgonlogic is now a maintainer of drush-vagrant, so let the consolidation commence!
Comment #4
ergonlogicSteven was nice enough to grant me commit access, so I'll start moving stuff over to a 2.x from aegir-up.
Comment #5
patcon CreditAttribution: patcon commentedLOVE 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:
And with that:
,
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 :)
Comment #6
patcon CreditAttribution: patcon commentedOh hey, and obviously, since we're all in lurve with drush, that command should totally be resurfaced as a drush command
Comment #7
ergonlogicI'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.
Comment #8
ergonlogicI'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.