28 posts tagged with "docker"

For about 1 year, we've been using DDEV for most of our Docker setups. While Sylius comes with its own Docker setup, I wanted to see if I could use DDEV to develop Sylius plugins as this would offer me a similar Docker experience to our other projects.

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"

One of my recent tasks was to run an upgrade of a production PostgreSQL database. Since we have PostgreSQL running in a Docker container in our Hashicorp Nomad environment, I assumed it would be enough to switch to a new Docker image and everything would be working fine.

Adding custom Javascript code to the Sulu Admin UI requires a rebuild of the administration interface frontend application. According to the Sulu docs, running the following command is enough:

bin/adminconsole sulu:admin:update-build

Sadly, this did not work in our ddev setup because ddev ships with a newer version of npm. Due to a breaking change for linked packages, Sulu is not compatible with npm > 6 at the moment.

In our Techradar we've listed DDEV as a tool to assess. But why?

Since we are currently moving to DDEV to standardize our Docker development setups, I was wondering how easy it will be to add my favorite Git Hook Manager CaptainHookPHP to the setup.

In Traefik providers are infrastructure components (e.g. container engines, cloud providers, or key-value stores) that can be queried in order to find relevant information about the routing configuration.

Sometimes one may face the need to restart a Docker container because it does not react anymore. While there are dozens of possible ways to accomplish this, I want to show the one we recently started to incorporate into our setups.

Sometimes, mostly for smaller customers, we deploy staging and production environments on the same machine. Not an ideal setup, but doable. Thanks to Docker the different instances can live in isolation, except of course when one instance takes the server down, the other instance is also affected.

Old PHP projects often still use Composer 1 and require an old PHP version to run. To make life easier for the other developers, I have created some efficient and small development setups based on Docker.