As developers, we're familiar with static analysis tools like PHPStan for identifying code problems. However, detecting runtime issues, especially those related to databases, requires a different approach.

When we first started using Nomad about 7 years ago, we quickly realized the need for Vault to handle secrets and certificates. Initially, we queried certificates from Vault during Docker image build time using a curl command.

I recently had to develop a tiny Odoo module and wanted to use DDEV for the task. Here's how I set up Odoo with DDEV.

As I work more intensively with coding agents, I've realized that a long-term memory is important. Without it, agents are limited to knowing only what's happened in the current session.

I recently updated our Gally DDEV addon to support the latest Gally 2.3 release. This new version brings exciting features like a recommender, visitor tracking, and search term suggestions.

On August 20th, the PHP Usergroup Rhein-Neckar metropolitan region is meeting again.

For years, we relied on an external ticketing service for selling unKonf tickets. When the service ceased to exist after COVID-19, we decided to build a custom Sylius platform to handle ticket sales. Initially, we used Sylius 1 but decided to migrate to Sylius 2 earlier this year due to the end of support for Sylius 1.

For a few months we've been using Onyx as an internal AI chat platform. Its advanced capabilities like RAG, web search, and deep research make it a valuable tool for us.

Standard code base search in coding agents like OpenCode can be very limited. To improve my daily workflow, I needed more advanced features like semantic search, call graphs, or an architectural overview.

How can I customize an existing Sylius Grid? That's a question that I got asked recently and decided to write about my learnings.