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.
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.
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.
In one of our recent projects, we are using Sulu CMS with the Sulu Headless bundle and a React frontend. Additionally, we are also using the Sulu Forms bundle for form handling.
Two weeks ago the bitExpert PHP team participated in the first API Platform Conference as part of our Learn&Grow initiative. Having built a number of projects based on the API Platform components already, we were keen to get the latest insights and learn from the core team about upcoming features.
As I have written before, we are big fans of Mark Shust's Docker Configuration for Magento project. Even though we customized the setup a bit for our needs, it comes with a lot of good stuff out of the box, like Xdebug support.
For a few projects we make use of the Event Engine by prooph software which is a biased - in a good way(tm) - way of quickly building event sourced applications. While building a user registration context, I was stuck a bit how and where to properly hash the password for the user. I could have done it in the init() method of the command, that way I would have made sure that the cleartext password is not "visible" anywhere in the application code. In the end, I decided to make use of a provider class. The return value of the provider will be passed to the specified aggregate method and allows me to pass it to the respective event.
We are big fans of Mark Shust's Docker Configuration for Magento project. We use a lot of our projects, the ones we start from scratch as well for ones that we have taken over and have some weird setup in place that we simply cannot get to work.
In a recent project, we make use of the Event Engine which is an Event Sourcing framework for PHP helping you to rapidly develop event sourced applications. Since parts of the exposed API by the Event Engine should be access proteced, we decided to use OAuth2 for access delegation. That way each route exposed by the Event engine application can be marked as "protected" if needed.