Past Meetup

PHP User Group Munich Meeting

This Meetup is past

77 people went

TNG Technology Consulting

Betastr. 13a · Unterföhring

How to find us

With S-bahn S8 to Unterföhring (10 Minute walk). Or Bus 233 to Betastrasse. (2 Minute walk). Lots of street parking available.

Location image of event venue


We're happy to announce our next community meetup on Wednesday, 24rd of May at 6.30pm. Our host will be TNG Technology Consulting GmbH.

Join us for interesting talks, fun discussions, and be part of the Munich PHP community!


6:30 - 7:00pm: socializing
7:00 - 7:45pm: first talk
7:45 - 8:00pm: break
8:00 - 8:45pm: second talk

Twelve-Factor Apps - Introduction, Best Practices, Live Demos
David Zülke, Heroku Inc.

Horizontal scalability has always been at the core of PHP application design, and in the cloud, that approach shines the brightest. But to fully leverage the power and convenience of PaaS offerings such as Heroku, it's worth following certain best practices and methodologies when developing applications. This presentation covers and demos the steps from code and dependency management over configuration to maintaining dev/prod environment parity.

David works at Heroku, a cloud platform as a service headquartered in San Francisco. He was already building applications for the Web when the dot-com bubble burst, and went on to co-own a software consultancy before exploring the e-commerce and Berlin startup scene. Based in Munich, Germany, he is a regular speaker at technology conferences around the world and an avid fan of all things fast or exciting.

Code fixing and automation
Sven Rautenberg, Vodafone Kabel Deutschland GmbH

When the daily duty of delivering working software is done with ease, and also secondary tasks like working tests are done well, there’s always more work waiting at the ‘nice to have’ priority level. Things like code style, valid Composer files, updated dependencies or various other meta data that isn’t at all mission critical, but always provides a certain level of annoyance if not maintained properly.

I’ll show you our way how to deal with such a situation when maintaining about 140 distinct repositories with PHP software. At this scale automation is the only choice, and we not only do it for testing, but for these maintenance tasks as well. We have created a single point of attack from where we can influence all our repositories and it’s code, and we do it in a way that is not as intrusive as pre-commit or pre-receive hooks, by using pull requests.

Sven has over 15 years of experience in PHP, and for the last 6 years, living in Munich, is developing applications at Vodafone Kabel Deutschland. He is writing groovy scripts at advanced rookie level to automate Jenkins, and constantly working on his gold badge for answering Composer questions on Stack Overflow. You can follow him on Twitter at @SvenRtbg.