We've been using a self-hosted GitLab instance for our customer projects since the end of 2015. We immediately jumped on GitLab CI when it was first released to replace our old Jenkins infrastructure with a more modern pipeline-as-code approach.
On October 31st, the PHP meetup Metropolregion Rhein-Neckar will meet again to discuss all things PHP.
I've been selected to speak at SyliusCon 2024 in November. At the conference, I will present a brand-new talk called "Simplifying Sylius Containerization with DDEV".
There are many applicable real-life scenarios where the destination page must sometimes be different upon the click of a button. Imagine the same button being clicked to determine what the destination page should be on its own. How to do this Intrexx?
In one of our current projects, we have to store sensitive user data in the database. Naturally, I was looking how to best encrypt the data in a Symfony & Doctrine application.
I've been selected to speak at SymfonyCon Vienna 2024 in December. At the conference, I will present a brand-new talk called "Simplifying Symfony Containerization with DDEV".
Recently, failures occurred randomly in our GitLab CI pipelines when pushing docker images to our internal Docker registry.
In the GitLab CI output, all I saw was the following error:
error parsing HTTP 499 response body: invalid character 'C' looking for
beginning of value: "Client Closed Request"
While checking the Magento log files of a Magento instance we recently migrated, I came across the following MySQL warning:
Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size
or decrease batch size value (which decreases memory usages for the temporary table).
Current batch size: 417; Allocated memory size: 40032000 bytes; InnoDB buffer pool size: 134217728 bytes.
Microsoft recently announced to retire the Office connectors in Microsoft Teams to deliver content from third-party services into a Teams channel.
On September 26th, the PHPUG Frankfurt meetup will meet again after our regular summer break with some interesting talks and discussions.