Hi WordPress, Meet Vagrant

16 thoughts on “Hi WordPress, Meet Vagrant”

  1. Hi Jeremy, thanks for doing this, it’s been on our plate to do this for a while, and we have various versions of it up on Github. Someone from our team will be reaching out to help shortly, expect issues/pull requests etc soon :).

    1. This is fantastic! I’m going to have to go GitHub spelunking. :)

      We’re very much willing to chat. IMO, the best solution would be for a maintained ZippyKid Vagrant repository on GitHub that you can point developers to that are working in the ZippyKid environment. Having this in a library of available Vagrant setups for WordPress would be amazing.

  2. I have yet to see where the added overhead of Vagrant would be worth it for me for most of the sites I work on.

    I do however see it’s value in it in some cases. For example I would really love to have a true perfect local representation of WP Engine’s server config. I love WPE, but FML I’ve bad more problems with server config there then anywhere else, except maybe Page.ly and their damned symlinks… come to think of it they all have their nuanced issues, but still vagrant configs maintained by the majors hosts (WP managed and otherwise) would be pretty cool.

    1. +1 to John’s comment. I’d love to see this. A vagrant file with WPE specs would be awesome! I’m sure $x developer on $y hosting platform would love to see this.

  3. Thanks for all of your work on this. I have been using this for a couple of sites and it has worked pretty well. One question I have is what is the default login info for the WordPress environment? I was able to login in a previous version, but I don’t remember how I did the initial set-up for a new site I am working on.

    1. It’s pretty amazing that I’ve forgotten to document that anywhere. :)

      Default user/pass combo for both installations is admin/password.

      Will add better docs on that to the next version. Thanks!

      1. You know, I bet you did document that somewhere at some point. Because I have been using this—and have logged in—after following your docs.

        Thanks for the awesomeness.

  4. Fantastic work here, guys. I’ve been using a hacky shell script + virtualbox for a while and have been wanting to switch over to vagrant, but never managed to find the time to get it working. Plus the rest of the dev team here at PMC has been wanting something exactly like this for quite a while, but what we have has worked “good enough” so we never managed to find the time.

    This makes is *so easy* to put together a standardized development environment without shuttling 1gb VM images back and forth, and *so easy* to get up and running with a new VM environment with all the tools we need.

    So, thanks for doing the hard part!

  5. So you have VVV up and running on your local machine and you want to replicate that setup (i.e. software (Ubuntu, nginx, PHP…) and its settings) on VPS (or any production setup).
    How?

    1. That’s going to be a bit tough with VVV. Theoretically, the provisioning script included could be run on a fresh Ubuntu 12.10 box and the proper software would be setup. You would likely need to do some additional work with config files.

      If you’re looking to do exact mirrors of production and development, it may be worth looking into other provisioners such as Salt, Puppet, or Chef. These do a more comprehensive job of maintaining the state of a machine through provisioning rather than the basic checks we do in VVV.

Leave a Reply