I started this project in order to allow the WordPress.org Theme Review Team (TRT) to better standardize on a reviewing environment. VagranTRT should give a unified platform for TRT members using Vagrant and should (hopefully) lead to faster theme review turn-around times.
- CentOS 6.5
- WordPress Developer Plugin, Theme Check Plugin
- WP-CLI
- MySQL
- PHP
- Nginx
- Apache
- Puppet
- WPTest test data
- Official Theme Unit Test data
If you’re on a Unix-based machine with a Bash shell, setup is pretty easy:
- Recursively clone the VagranTRT repo. This will create a directory named
vagrantrtby default.- E.g.
git clone https://github.com/zamoose/vagrantrt --recursive
- E.g.
- Change into the
vagrantrtdirectory. - Run
vagrant up. - Wait for a bit.
- Log in to your new Vagrant VM via
vagrant ssh. - Have fun!
- root:blank
- wordpress:wordpress
- wordpress2:wordpress2
- wordpress_multi:wordpress_multi
- wordpress:wordpress
The Vagrant CLI documentation will be useful for developers that haven't used Vagrant before.
Some useful commands:
vagrant up- Start and provisions the VMvagrant halt- Stops the VMvagrant reload- Restarts and provisions the VMvagrant provision- Provisions the VMvagrant ssh- Logs into the VM with sshvagrant destroy- Deletes the VM
The puppet modules are all set up as submodules in puppet/modules. In general, you shouldn't have to worry about this because the vip-init script will update the submodules automatically. Just noting here for documentation purposes at this point.
I have stood upon the shoulders of giants -- much of the inspiration and format of this project is based upon the hard work those contributing to the VIP Quickstart project have put in and I thank them greatly for that work.
The following projects are either inspirations, Git submodules employed in this project, or the very tools the project itself is built upon: