Skip to content


Folders and files

Last commit message
Last commit date

Latest commit



87 Commits

Repository files navigation

Vagrant Config for TYPO3 Flow Development

My default Linux box for PHP development with TYPO3 Flow (but should work with other PHP stuff, too).

The usual approach (ok, seen more-often than mine) is to have one Vagrant based system per project. While that makes perfectly sense in many situations, I needed something different: I'm working on many smaller projects during my spare-time and based on that, my Vagrant setup suffices the following requirements:

  • I need to be able to work offline, e.g. in the train
  • I want a minimum overhead for creating a new "site" or virtual host
  • I prefer the GUI Git client (Tower) over the command line - so the project files shall remain locally on the host system
  • I want a documented and recoverable setup of the VM

For that I thought of a solution based on Apaches *vhost_alias" module, which allows me to call whatever domain name I want - and it will be dynamically mapped locally. E.g. for a request for "", Apache will look in the document-root at "/var/www/" - without having to declare that in a vHost directive for each new project. Just let the DNS or hosts file point to the IP of the Vagrant box and you're ready to go. The subdirectory "vHost" of this repository is mounted as /var/www in the guest OS.

This changed with version 2: Until v1.x the box shipped both Apache and Ningx at the same time - but since I've never used Apache anymore on my dev-system, I've dropped it for v2.0 and chose nginx as the default web server.


Install Vagrant with the installer that fits your hosts operating system.

Download and Install VirtualBox

Clone this repository

git clone git://

Change to the cloned repository

cd VagrantTYPO3Flow

Boot up the virtual box:

vagrant up

The box gets the static IP addresses which is only accessible from your local computer.

Now add any project you're working on (e.g. "") to your hosts file and let it point to - and create a directory with the domain name within the sub-directory "vHosts". As soon as you call that domain from your browser, you should see it working. As an alternative to editing your hosts file over and over again, you can of course also install dnsmasq on your host system.

For name resolution from within the guest system (e.g. within the vagrant box), the dnsmasq tool is installed and configured so that lookups to *.dev, *.prod and *.lo will always result in the IP of Nginx (

For demonstration purpose, I've added "phpconfig.lo" already, as soon as you let that name point to the IP, you should see some phpinfo() output when accessing "phpconfig.lo" with your browser.

To log in via SSH, just execute the following command from within the current directory:

vagrant ssh

If you fiddle around/extend/change/improve with the Puppet manifests contained in here, you can simple re-run the puppet apply command from outside of the VM with the following command (instead of rebooting the VM):

vagrant provision

What it contains:

  • Ubuntu 14.04 LTS (trusty)
  • PHP 5.5.x
  • MySQL server 5.5.x (user: root, password vagrant)
  • Remote-Access for MySQL
  • Nginx 1.4.x with mass host config
  • dnsmasq config (for local name resolution within the vagrant-box)
  • phpMyAdmin ( - or any other "domain" that points to this IP)
  • mailcatcher ( a "Mock SMTP-Server" that catches all Mails sent to it and makes them available via a web-frontend (perfectly suited for testing applications that send mails
  • nano-Editor
  • git and tig
  • Composer (installed + kept up to date)
  • Node including npm and Bower
  • OpenLDAP Server, LDAP CLI Tools and PHP LDAP-Module
  • Redis Server
  • Beanstalk Daemon
  • Supervisor Daemon

MySQL access from "remote":

Sometimes, the included phpMyAdmin installation is not enough and you want to connect to the DB from your host system (from outside of the box). To do that, just run the following command to connect to the MySQL database that runs inside of the box:

mysql -h -u root -pvagrant

LDAP Server configuration:

If you want to use LDAP, you should reconfigure the package with the following command:

dpkg-reconfigure slapd

Basically to set your username/password to connect to your new OpenLDAP-Server.

Beanstalk MessageQueue Daemon:

For storing any tasks or notes in a message queue, Beanstalk is installed and listening on on port 11300.

Supervisor Daemon:

If you need to test applications that execute one or more tasks in parallel and keep running/restarted after exiting, supervisor is your friend.

See manifests/default.pp for a sample task configuration (needs to be uncommented and you're ready). See the log file at /var/log/supervisor/supervisord.log to see what happens.

Where it was tested:

  • Windows 7 with VirtualBox v4.3.6 and Vagrant v1.4.1
    • Attention You need to disable sendfile in the Nginx config, see the note in the config file, when running this box on a Windows host!


The following stuff is what I want to add to this box:


Optional and maybe later:

  • xDebug
  • adminer instead of phpMyAdmin
  • zsh with oh-my-zsh

How to contribute?

Feel free to file new issues if you find a problem or to propose a new feature. If you want to contribute your time and submit an improvement, I'm very eager to look at your pull request!

In case you want to discuss a new feature with me, just send me an e-mail.


Licensed under the permissive MIT license - have fun with it!

Can I use it in commercial projects?

Yes, please! And if you save some of your precious time with it, I'd be very happy if you give something back - be it a warm "Thank you" by mail, spending me a drink at a conference, send me a post card or some other surprise :-)


Vagrant config for PHP development







No releases published


No packages published