All Projects → tierra → Wp Vagrant

tierra / Wp Vagrant

WordPress Vagrant boxes for testing PHP 5.3, 5.4, and 5.5

Labels

Projects that are alternatives of or similar to Wp Vagrant

Puppetlabs Openstack
Puppet Labs Reference and Testing Deployment Module for OpenStack (master tracks Kilo)
Stars: ✭ 95 (-30.15%)
Mutual labels:  puppet
Jerakia
A pluggable and extendable data lookup system
Stars: ✭ 111 (-18.38%)
Mutual labels:  puppet
Puppet Mcollective
MCollective Server and Client Puppet Module
Stars: ✭ 121 (-11.03%)
Mutual labels:  puppet
Hiera Http
HTTP backend for Hiera
Stars: ✭ 95 (-30.15%)
Mutual labels:  puppet
Govuk Puppet
Puppet manifests used to provision the main GOV.UK web stack
Stars: ✭ 109 (-19.85%)
Mutual labels:  puppet
Loom
Elegant deployment with Fabric and Puppet.
Stars: ✭ 115 (-15.44%)
Mutual labels:  puppet
Puppet Mongodb
mongodb installation
Stars: ✭ 90 (-33.82%)
Mutual labels:  puppet
System Config
MOVED: Now at https://opendev.org/opendev/system-config
Stars: ✭ 128 (-5.88%)
Mutual labels:  puppet
Simp Core
The base SIMP build repository
Stars: ✭ 111 (-18.38%)
Mutual labels:  puppet
Puppetlabs spec helper
A set of shared spec helpers specific to Puppetlabs projects
Stars: ✭ 121 (-11.03%)
Mutual labels:  puppet
Vagrant Baseline
Dev sandbox with batteries included
Stars: ✭ 100 (-26.47%)
Mutual labels:  puppet
Puppet Gluster
puppet module for gluster
Stars: ✭ 104 (-23.53%)
Mutual labels:  puppet
Puppet Debugger
A interactive live debugger and REPL for the puppet language
Stars: ✭ 117 (-13.97%)
Mutual labels:  puppet
Puppet R10k
Setup and configure r10k for use with git based environments in puppet
Stars: ✭ 95 (-30.15%)
Mutual labels:  puppet
Serverfarmer
Manage multiple servers with different operating systems, configurations, requirements etc. for many separate customers in an outsourcing model.
Stars: ✭ 122 (-10.29%)
Mutual labels:  puppet
Drupal Lxc Vagrant Docker
Deploy and develop on Drupal with LXC, Vagrant and Docker. Includes: nginx,php-fpm,apc,xhprof,mysql,phpmyadim,composer
Stars: ✭ 94 (-30.88%)
Mutual labels:  puppet
Puppet Nodejs
Puppet module to install nodejs and global npm packages
Stars: ✭ 111 (-18.38%)
Mutual labels:  puppet
Onceover
Your gateway drug to automated infrastructure testing with Puppet
Stars: ✭ 132 (-2.94%)
Mutual labels:  puppet
Salt Sandbox
A Vagrant-based Salt development environment for creating new modules
Stars: ✭ 122 (-10.29%)
Mutual labels:  puppet
Cis Puppet
Center for Internet Security Linux Benchmark implementation for PuppetLabs
Stars: ✭ 117 (-13.97%)
Mutual labels:  puppet

WordPress Vagrant Boxes

While we're fans of the popular VVV project, this Vagrant configuration takes a different approach. We like to think that VVV is great for up-to-date development tools, working on plugins and themes, and building entirely new websites. However, this configuration was built for the purpose of testing and debugging mostly WordPress core, and ensuring compatibility with older (but still supported) server configurations.

This configuration also doesn't make any assumptions about your preferred development workflow. It does not checkout or install WordPress at all. It's up to you if you would like to unpack and install a ZIP, checkout from SVN, or clone from git. However, the web server is preconfigured to look for WordPress in a specific location.

Configurations Provided

wordpress-php53

  • Ubuntu 12.04 (precise)
  • Apache 2.2.22 (suPHP, port 80 and 443)
  • PHP 5.3.10
  • PHP Extensions: curl, gd, imagick, mcrypt, mysql, xdebug
  • PHPUnit 4.8.36
  • MySQL 5.5.50
  • Subversion 1.6.17, Git 1.7.9.5
  • Node.js 6.12.0, Grunt

wordpress-php54

  • Debian 7.8 (wheezy)
  • Apache 2.2.22 (suPHP, port 80 and 443)
  • PHP 5.4.45
  • PHP Extensions: curl, gd, imagick, mcrypt, mysql, xdebug
  • PHPUnit 4.8.36
  • MySQL 5.5.50
  • Subversion 1.6.17, Git 1.7.10.4
  • Node.js 6.12.0, Grunt

wordpress-php55

  • Ubuntu 14.04 (trusty)
  • Apache 2.4.7 (suPHP, port 80 and 443)
  • PHP 5.5.9
  • PHP Extensions: curl, gd, imagick, mcrypt, mysql, xdebug
  • PHPUnit 4.8.36
  • MySQL 5.5.50
  • Subversion 1.8.8, Git 1.9.1
  • Node.js 6.12.0, Grunt

Getting Started

  1. Install both VirtualBox and Vagrant.
  2. Clone this repository to a convenient location for your development:
    • git clone https://github.com/tierra/wp-vagrant.git
    • cd wp-vagrant
  3. Check out (or clone) the develop repo to the wordpress folder:
    • svn checkout https://develop.svn.wordpress.org/trunk wordpress or
    • git clone git://develop.git.wordpress.org/ wordpress
  4. Add the following to your hosts file:
    • 192.168.167.10 wordpress-php53.local
    • 192.168.167.11 wordpress-php54.local
    • 192.168.167.12 wordpress-php55.local
  5. Start Vagrant: vagrant up [box]
    • Without naming a box, just the wordpress-php55 box will be started. Specify wordpress-php53, or wordpress-php54, to start up instead.

Note that Apache is configured to point to the wordpress/build directory, so you need to remember to run grunt from the WordPress directory after checking out the code. Optionally, you could also just install WordPress normally inside the wordpress/build directory without using the develop repository. All boxes are pre-configured with Node.js and Grunt, so if you don't have these tools installed locally, you can just SSH into the box, and run the following:

cd /vagrant/wordpress && npm install && grunt

With any of the boxes started, you can reach them at these locations:

MySQL Configuration

The MySQL root password is "wordpress", and all boxes come with two pre-configured databases:

  • wordpress (this is meant for a regular installation)
  • wordpress-tests (this is meant for use with PHPUnit tests)

A single account with rights to all databases for convenience:

  • Username: wordpress
  • Password: wordpress
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].