We started developing a few Sulu based projects. In this blog post, I want to share how we have configured our GitLab CI build pipeline to validate, build, and deploy our Sulu projects.

France is more than just cheese, wine, and the Eiffel Tower. Our neighbors know not only how to develop excellent PHP Frameworks, but also how to organize awesome conferences!

A part of our PHP-Team took the chance to attend the API Platform Conference 2022 in person, which took place in Lille (France).

Not being happy with our current Docker build process in one of our projects, I was researching how to optimize the process.

Recently, I wanted to improve our CI build pipelines with some custom-built Docker images for our PHP projects. To make sure I can reuse the image in as many of our projects as possible, I wanted to compile and install as many PHP extensions as possible.

It's been a few months sine we migrated from Silverstripe to Docusaurus for our blog. Quite a few blog posts have been published since then via the CI pipeline we've set up. This blog post covers how we do things.

While testing an async method with ts-jest I came across a problem. The method throws an error on invalid input.

An interview about the work of the PHP Chapter

PHP is the server-side programming language that powers most of our customer projects. It is part of our toolchain since bitExpert was started in 2003. Over the years PHP has evolved a lot, it is far away from being the scripting language it used to be some 20 years ago.

We took this opportunity to talk about this great language with our PHP chapter lead, Holger Dörner.

We are currently building our first website based on Sulu. For this, we use the Sulu headless bundle to focus on React as technology on the frontend side.

After my first in-person event this year, I am quite happy to be able to speak again on a stage in front of "real people"(tm) at a conference in September.

For a client, we also handle the vulnerability management of the projects. This also involves manual checks after a new project is launched, to ensure that no critical security problem is caused by misconfiguration.