There's one plugin for Vagrant which I love to promote in my talks and this is the Cachier plugin. When giving my talks and mentioning the plugin I realized that not many people are aware of the plugin. That's the main reason I write the following lines. The downside of Vagrant is what whenever you destroy a virtual machine and build it again all packages (eg. .deb packages for the OS or Composer packages for the application) need to be downloaded again. Downloading and installing a lot of packages can be quite time consuming which in turn means developers try to avoid it. Which in turn means no one regularly checks if provisioning of the virtual machine still works as it should. The Cachier plugin is the solution for that problem. As the name implies the plugin will cache the downloaded packages and re-use them when possible. To achieve that the plugin will link several folders of the virtual machine back to the host, so that the packages are actually stored on the host, not the vm. Very clever.

Currently, we have to refactor some parts of an ExtJS4 application for one of our clients. During the refactoring process we renamed some namespaces to fit the current naming schemes, which changed a little bit over the time.

Inspired by Ben Ramsey's blog post I thought I should share my PHP story as well. I discovered PHP in late 1999. Back then I was looking for an alternative to Perl which I used back in those days to "hack" smallish web applications. I did not really like the syntax of Perl (sorry) and it was always hard to debug on most web hosts. By accident I found PHP and loved it, well in fact I still do love it. I used PHP in 2001 in my first job where I had to develop a web-based DNS management system which was the biggest project for me back in those days.

Every now and then when provisioning a virtual machine with Vagrant I got an error during the provisioning process. Everything seemed to work fine but the error confused me and my developers so I was looking for the source of the error. I came a across a Vagrant bug report where Mitchell Hashimoto explained that "the reason this error message even appears is due to a bug in Ubuntu not checking whether stdin is a TTY, and just assuming it is". One of the comments in the discussion of this "bug" proposed a "bugfix" by adding the following line to the VagrantFile. Up to now this fix works fine for us and you might use it as well:

Vom 01.12.2015 bis zum 02.12.2015 findet in Köln die SMART DATA Developer Conference 2015 statt. Ich freue mich dabei zu sein und meinen Vortrag "PostgreSQL: Die NoSQL Datenbank die niemand kennt" präsentieren zu dürfen. Zusätzlich zum Vortrag werde ich am 01.12 einen Workshop "NoSQL mit PostreSQL" anbieten und freue mich auf interessierte Teilnehmer.

Forced Motivated by Robert Reiz and his blog post about how to set-up a Vagrant environment I thought that it`ll be a good idea to quickly outline how we typically configure Vagrant in our projects. The bare minmium VagrantFile looks like this:

Am Dienstag den 30.06.2015 trifft sich die node.js Usergroup Mannheim wieder bei uns. Anmeldungen bitte auf der entsprechenden meetup.com Seite vornehmen. Danke!

Nachdem wir vor einiger Zeit unsere CAO Faktura Version auf die Version 1.4.4.177 aktualisiert haben, ist es uns nicht mehr möglich Zahlungen für Einkäufe zu stornieren. Beim Versuch einen Storno ausführen wird die Fehlermeldung "Für diese Operation fehlen Ihnen die Rechte!" angezeigt, obwohl alle nötigen Rechte im CAO-Admin vergeben waren. Nach einer kurzen E-Mail Konversation mit dem Entwickler von CAO-Faktura war die Lösung recht einfach. Es ist folgendes SQL Statement in der Datenbank auszuführen:

The PHPUnit manual shows how to define a set of browsers for a specific unit test like this:

Recently we ran into an issue with SVG rendering in an Cordova-based Sencha Touch application. When switching back and forth between views in a TabPanel SVG images got messed up. The problem only appeared on "older" Android devices (<= 4.1.2) and only when the images were embedded via an <img> tag. The solution was simple: Replace every <img> tag with an <div> container and include the SVG image via the CSS property background-image.