Am Donnerstag den 16.10.2014 trifft sich die RheinMainJS Usergroup ab 19 Uhr bei //SEIBERT/MEDIA in Wiesbaden. Ich bin als Sprecher dabei und werde in meinem Vortrag "ExtJS 5 MVVM - WTF? FTW!" auf die neuen Features von ExtJS5 eingehen und von unseren Projekterfahrungen berichten.

Recently we converted one of project to use Vagrant Rsync Folders instead of the default VirtualBox shared folder setup. After running the vagrant rsync-auto command for a while we realized that the symlinks in Composers ./vendor/bin/ where replaced with the content of the previously symlinked files. This made the commands unusable.

Since quite a while Vagrant has support for syncing folders via rsync. While it is quite easy to set things up on a linux box, I was struggling a bit to get things going on a windows host. As the vagrant docs recommended I installed rsync and ssh client via the Cygwin package. After running "vagrant up" I got an error from the Vagrant rsync plugin stating "No such file or directory". Via Google search I came across a bug report on Github. As it turns out the problem seems to occur because Vagrant "tries to be smart and detect the environment but it obviously doesn't work reliably". The proposed solution is to patch the Vagrant ruby sources. You have to edit the file C:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.6.3\plugins\synced_folders\rsync\helper.rb and change line 43 to:

Recently I needed to run a script on server via SSH. To automate things I wanted to execute the script via Phing. The command I wanted to execute looked like this:

Recently we were in the need to create (and host) an own npm module. Setting up a private repository with sinopia seemed like a bit too much work for hosting just a single npm package. So I decided to use the built-in functionality of npm to directly refer to a git repository in the package.json file. This worked fine on "my machine" but failed on my co-workers machine. It turned out that we were both using the same version of nodejs and npm but we were running different versions of git. I had a recent version of git running. My co-worker's git version was pretty old (1.7.x). I advised that we should upgrade git any try again. And guess what, after the upgrade npm install worked perfectly fine.

Vom 26.10.2014 bis zum 29.10.2014 findet in München die International PHP Conference 2014 statt. Ich freue mich als Sprecher dabei sein zu können und meine Vorträge "From Vagrant to Production" und "The seven deadly Sins of Dependency Injection" präsentieren zu können.

Vom 03.10.2014 bis zum 05.10.2014 findet in Manchester die PHP North West Conference 2014 statt. Ich freue mich als Sprecher dabei sein zu können und meinem Vortrag "Composer for corporate use" präsentieren zu können.

Bereits zum zweiten Mal findet in Nürnberg die Developer Week statt. Die Konferenz findet vom 14.07.2014 - 17.07.2014 im Nürnberg Convention Center NCC Ost statt und vereint die drei Sub-Konferenzen die NET Developer Conference, die Mobile Developer Conference und die Web Developer Conference. Ich freue mich mit meinem Vortrag "PostgreSQL: Die NoSQL Datenbank die niemand kennt" dabei zu sein. Der Vortrag zeigt auf wie man PostgreSQL als NoSQL Datenbank einsetzen kann und stellt dar warum dies in bestimmten Situationen durchaus Sinn machen kann.

Paul M. Jones asked me to go into detail and explain my thoughts on the Action-Domain-Response pattern, particular why I think action classes make more sense than the commonly used controller classes.

Since we have to deal with a lot of private packages which cannot be shared on packagist I set-up a private Satis repo. Whenever a new version of a package gets created the Satis build process is started by our Jenkins build server. In the last couple of months this process takes quite a while because Satis rebuilds the index for every repo it knows about. Since we deal with quite a few repos containing a large amount of versions it slowed down the "build time". Obviously it does not make any sense to run Satis on a repo that has not changed. Since Satis was lacking this feature I started hacking on it and I am happy that the feature got merged into master this morning. If you have to deal with large repos or a large number of repos you might want to give it a try.This is how things work: