Skip to content
Branch: master
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
79 lines (52 sloc) 2.78 KB


If you run into any problems with the instructions below, check out the Troubleshooting guide.

Initial Setup

  1. Setup Varying Vagrant Vagrants.

    We recommend that you follow the step to install the vagrant-hostsupdater plugin, because if you don't then you will need to manually add the hostnames for each WME site to your local hosts file.

    Make sure you have the latest version of VirtualBox, Vagrant, and VVV.

  2. Verify that VVV is working

    Open http://vvv.test/ in your browser, and make sure it loads. Then click on one of the links under Bundled Environments, and make sure that it loads too.

    If you run into any problems, stop and fix those before trying to install the Meta Environment.

    Once VVV is working, then you can move on to the next step.

  3. Check if you have a vvv-custom.yml file in the vagrant-local folder.

    If you don't, then create one by copying the default vvv-config.yml file:

    cp vvv-config.yml vvv-custom.yml

    Then uncomment the following lines inside vvv-custom.yml:

    #  repo:

    ...and extend them so that they look like:

      description: "An environment useful for contributions to the WordPress meta team."
        - wp-meta.test
          "buddypressorg.test": true
          "jobs.wordpressnet.test": true
          "wordcamp.test": true
          "wordpressorg.test": true
          "wordpresstv.test": true

    This will provision all sites. Use false to skip provisioning of specific site.

  4. Restart and re-provision VVV

    1. vagrant reload --provision
    2. This will take roughly 10-30 minutes

You're all set!

  • Visit http://wp-meta.test for links to all the available sites.
  • Log in to any of them with username admin and password password


When new sites are added to the repository, you'll need to pull the changes, then re-provision your local copy in order to obtain the new site.

  1. cd vagrant.local/www/wordpress-meta-environment
  2. git pull origin master
  3. If the new site is not part of an existing multisite/multi-network installation, then you can simply run vagrant reload --provision
  4. If the new site is part of an existing installation (like wordpressorg.test), then you'll need to delete the public_html folder and database for that site, and then run vagrant reload --provision
    1. ⚠️ Don't forget to backup any uncommitted patches that you're working on.
You can’t perform that action at this time.