At the last meetup of the Berlin PHP Usergroup, Christoph gave a talk about Vagrant. Good enough of a reason to write down or re-cap some things I’ve learned with or about Vagrant over the last two years. Base boxes There are lots of base boxes available, but don’t be tempted to rely on them (e.g. via config.vm.box_url). Vagrantbox.es doesn’t actually mirror images and that is a huge pain. Available base boxes tend to be outdated....
Development, testing, staging and production — this is how most people devide up different environments for application development. Maintenance and setup of these environments is often not a trivial goal to achieve. Having worked with a couple different code bases and setups over the last decade, I often noticed things like environment specific hacks (if ($env == 'testing') { ... }) in application code and service configurations and a lot of manual labour all around....
When I ran our setup on an instance the other day, I noticed how it failed with a “package not found” (or similar) error. After debugging this a bit, we discovered that Karmic moved from “archive.ubuntu.com” to “old-releases.ubuntu.com” (Probably diskspace or something — but who knows? :-)). And because the sources pointed to the former, it broke the bootstrap process on new and existing EC2 instances and Vagrant VMs for us....
I swore myself to only post meaningful stuff to this blog, so basically, no rants, ever. But! The discussion revolving around Twitter and Rails (versus Scala) did remind me of something: If you’ve doing PHP for a while and know people who are programming not in PHP, you probably heard it all before. PHP guys (and girls) are being look down on and mocked by people of other programming and scripting languages....