Since more than one year we moved from eGroupWare to Tine 2.0. After using eGroupWare for more than 5 years it was time to look for an alternative. Integrating Tine 2.0 into our it infrastructure was no big deal, it was even possible to connect it to our central LDAP server. The LDAP sync of Tine 2.0 is designed in a way to copy all user and group information from the LDAP server into the local Tine 2.0 database. The sync process is triggered via a cronjob. Since we have a lot of LDAP groups for the various applications we use, I was looking for a way to filter groups that should be synced. I realized there was no way of ignoring certain groups so I changed my plan and added some custom code which would at least hide the groups.
To accomplish that open the file Tinebase/Group.php and locate the syncGroups() method and look for the line
After trying to get a few application to run on hhvm I came across the following error:
As I blogged recently we solved the HTTP Basic Auth problem with Composer / Satis by using expect. I still like the general idea but expect can be a bit tricky to configure. For those of you who are not happy with that solution this one might be a good alternative: As I helped out Manuel Lemos to create an Composer Installer for phpclasses.org packages he pointed out that the new Composer Plugin API might make it easier to extend Composer and offer authentication support. And yes he was right ;) As I had some spare time last weekend I extracted the code handling the authentication logic from his installer and created a separate plugin which can be found on github and packagist.org.
UPDATE (04/2014): Since Facebook decided to remove the webserver functionality from the "official" binaries this howto will not work anymore! Read here how to set things up with the current version of hhvm.
Am Donnerstag den 30.01.2014 trifft sich in Frankfurt die PHP Usergroup Frankfurt. Ich freue mich als Sprecher dabei sein zu dürfen und werde erzählen wie man PostgreSQL als NoSQL Datenbank nutzen kann und warum das sinnvoll sein kann.
A couple of weeks ago we relaunched our new website. In addition to that we decided to relaunch our blog as well. Since we wanted to use Silverstripe as CMS for our main website it made sense to use Silverstripe as a basis for our blog as well. Luckily there exists a blog module for Silverstripe which made it pretty easy to set-up this blog. The migration was no-brainer: Export the existing Wordpress content as XML file and import the XML file into Silverstripe via the wordpressimport module. The documentation of the wordpressimport module said it would be enough to add the following RewriteRule to the .htacess file:
Am Montag den 10.02.2014 findet in Karlsruhe wieder einmal der Webmontag Karlsruhe statt. Ich freue mich als Sprecher dabei sein zu dürfen und berichten wie man PostgreSQL als NoSQL Datenbank nutzen kann und warum das sinnvoll sein kann.