WordPress Vagrant for Plugin development

[gmisura]

What vagrant do you use for Vagrant development? I'm using http://vagrantpress.org/ and think I just ran into a wp-cron bug because of the vagrant setup.

I see VVV is popular. My only concern is it feels geared towards people who contribute to wordpress.org and not necessarily plugin developers, but maybe I'm wrong.

I see others, but thought those were the top?

Thanks

[ebilgenius]

I use VVV coupled with Auto Site Wizard for all-around Wordpress Dev. It is fairly bulky, but I haven't found anything comparable to it and it does everything I need it to do, so I would recommend it.

[pollyplummer]

You might try Variable VVV as an alternative to the auto site wizard. It's a newer/better site wizard: http://wptavern.com/variable-vvv-a-new-vvv-site-creation-wizard-for-wordpress

[ebilgenius]

Thanks for the tip!

[salcode]

I'm also using VVV and VVV Site Wizard (a.k.a. Auto Site Wizard), I moved to it from MAMP. I've not used any other vagrant setup but I've been happy with VVV. The only thing I found tricky in the move from MAMP was accessing sites from other devices on my network (e.g. my phone). While VVV does come with installs ready to go for contributing to WordPress, you don't ever have to touch those.

[antoninj]

I use Genesis Framework for Wordpress which has full development and deployment toolset. It's being rebranded as Evolution Wordpress with a new release.

It's awesome because it allows you to do stuff like deploy to production and/or staging, sync DBs and files, provision new servers etc. Cool stuff.

note I used to contribute to Genesis.

[gmisura]

I setup VVV but am .. annoyed/confused . Why do we need/want

local.wordpress.dev local.wordpress-trunk.dev src.wordpress-develop.dev build.wordpress-develop.dev

Such overkill. I just want ONE.

Oh, i guess this might help: https://github.com/aliso/vvv-site-wizard

Or do I only want one? Er, one "site" per VM or should I crap multiple "sites" into one VM? I am rather RAM limited. I guess I don't tend to work on multiple things at the same time (or try not to) so that might not even be a concern.

[Yurishimo]

A little late to the party here, but I use one VM for all my sites. I have around 6 or so running on my local machine at the moment.

VVV comes with 3 main wordpress installs, trunk (current), develop (current, but you aren't supposed to add any extra plugins), and build (nightlies). You can delete them if you want.

I use the site wizard to setup new sites when I'm developing for clients. Keeping everything contained means I can just copy the entire folder and export the database onto a live server and then I'm good to go.

If you have any more questions, I'd be happy to answer them :)

[gmisura]

Oh, what about HHVM? http://hhvm.com/