Vagrant LAMP

My default LAMP development stack configuration for Vagrant.

Requrements

• Virtualbox
• Vagrant >= 1.7.0
• vagrant-omnibus plugin

Installation:

Download and install VirtualBox

Download and install vagrant

Install vagrant-omnibus plugin

$ vagrant plugin install vagrant-omnibus

Clone this repository

Go to the repository folder and launch the box

$ cd [repo]
$ vagrant up

What's inside:

Installed software:

• Apache
• MySQL
• Redis
• php
• phpMyAdmin
• Xdebug with Webgrind
• zsh
• git, subversion
• mc, vim, screen, tmux, curl
• MailHog
• Composer
• Phing
• Wordpress utils:
  • WP-Cli
  • wp2github.py
• Magento utils:
  • n98-magerun
  • modman
  • modgit
• Node.js with following packages:
  • Grunt
  • Bower
  • LESS
  • CSS Lint

Notes

Apache virtual hosts

You can add virtual hosts to apache by adding a file to the data_bags/sites directory. The docroot of the new virtual host will be a directory within the public/ folder matching the host you specified. Alternately you may specify a docroot explicitly by adding a docroot key in the json file.

Default preconfigured host is local.test.

Accessing your hosts via your local web browser

In order to access vagrant hosts via your local browser you will need to edit your hosts file (/private/etc/hosts in Macs, c:\Windows\System32\Drivers\etc\hosts in Windows, /etc/hosts in Linux). All hosts should be mapped to 192.168.33.10:

192.168.33.10 local.test someyourotherhost.test

MySQL

The guests local 3306 port is available on the host at port 33066. It is available on every domain. Logging in can be done with username=root, password=vagrant.

phpMyAdmin

phpMyAdmin is available on every domain. For example:

http://local.test/phpmyadmin

XDebug and webgrind

XDebug is configured to connect back to your host machine on port 9000 when starting a debug session from a browser running on your host. A debug session is started by either by appending GET variable XDEBUG_SESSION_START to the URL or setting XDEBUG cookie (if you use an integrated debugger like Eclipse PDT it will do this for you).

XDebug is also configured to generate cachegrind profile output on demand by adding GET variable XDEBUG_PROFILE to your URL. For example:

http://local.test/index.php?XDEBUG_PROFILE

Webgrind is available on each domain. For example:

http://local.test/webgrind

It looks for cachegrind files in the /tmp directory, where xdebug leaves them.

Note: xdebug uses the default value for xdebug.profiler_output_name, which means the output filename only includes the process ID as a unique part. This was done to prevent a real need to clean out cachgrind files. If you wish to configure xdebug to always generate profiler output (xdebug.profiler_enable = 1), you will need to change this setting to something like

xdebug.profiler_output_name = cachegrind.out.%t.%p

so your call to webgrind will not overwrite the file for the process that happens to serve webgrind.

MailHog

All emails sent via local mail transport are intercepted by MailHog. So normally no email would be delivered outside of the virtual machine. Instead you can check messages using web frontend for MailHog, which is running on port 8025 and also available on every domain:

http://local.test:8025

Composer

Composer binary is installed globally (to /usr/local/bin), so you can simply call composer from any directory.