My default LAMP development stack configuration for Vagrant.
- Vagrant >= 1.7.0
- vagrant-omnibus plugin
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
- Xdebug with Webgrind
- git, subversion
- mc, vim, screen, tmux, curl
- Wordpress utils:
- Magento utils:
- Node.js with following packages:
Apache virtual hosts
You can add virtual hosts to apache by adding a file to the
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.
The guests local 3306 port is available on the host at port 33066. It is also available on every domain. Logging in can be done with username=root, password=vagrant.
phpMyAdmin is available on every domain. For example:
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 appending GET variable XDEBUG_SESSION_START to the URL (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:
Webgrind is available on each domain. For example:
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
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.
ll 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:
Composer binary is installed globally (to
/usr/local/bin), so you can simply call
composer from any directory.