How to Test Gitlab CI Pipelines locally in 2025
Three years ago I wrote a post about how to test GitLab CI pipelines locally. Unfortunately, GitLab discontinued this feature some time back as part of the Runner application's refactoring process.
Three years ago I wrote a post about how to test GitLab CI pipelines locally. Unfortunately, GitLab discontinued this feature some time back as part of the Runner application's refactoring process.
To have the most flexibility for our CI pipelines, we use the Docker runner in our GitLab CI environment. This allows us to easily customize each job in each build pipeline for each of our customers, ensuring they match our specific needs.
We use DDEV for almost all of our PHP projects. Also, we use FrankenPHP in our projects, but so far only in production.
Can we make FrankenPHP also run in DDEV to have a more consistent development environment?
One year ago, IONOS Cloud added a new feature to their Container registry: Vulnerability Scanning. This blog post will give you an overview of how the feature can be used in your software development workflow.
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".
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".
In a recent project, we dealt with 2 DDEV instances — 2 applications that need to communicate with each other or, more specifically, exchange files.
Following our guide to set up Traefik, Docker, and Compose with multiple networks, I ran into a problem:
a network with name customer_staging_default exists but was not created for project "customer_staging"
Set `external: true` to use an existing network
network customer_staging_default was found but has incorrect label com.docker.compose.network set to "staging_default"