DazzLog

S6-overlay is a container-focused process manager that offers end-to-end management of the container’s lifecycle, from initialization to graceful shutdown. To make use of s6-overlay we need to add the binaries to our container by adding, extracting and then moving them to the directory where they are expected. ADD https://github.com/just-containers/s6-overlay/releases/download/3.2.0.0/s6-overlay-noarch.tar.xz /tmp ADD https://github.com/just-containers/s6-overlay/releases/download/3.2.0.0/s6-overlay-x86_64.tar.xz /tmp Update dependencies When adding the s6-overlay sources to in a Dockerfile we want to make sure that we get notified when a new version is available, so we can always be up-to-date with all our libraries.

Continue reading 

When you divert from Symfony’s standard structure there are some things that do not work out of the box anymore. One of it is routing. Default Symfony If you start a fresh Symfony project you will be presented with the following stricture: app/src ├─ Controller ├─ Entity ├─ Repository └─ Kernel.php The routing config looks like this: # app/config/routes.yaml controllers: resource: path: ../src/Controller/ namespace: App\Controller type: attribute So the Controller directory is the place all controllers go you might think first.

Continue reading 

I have developed a Symfony Web-Application, and it runs locally in a dockerized environment with docker-compose. This app is going to be deployed to production as a docker container. In production the handling of environment variables and how they are passed to the container during development is different. 12 Factor App A few points from the 12factor methodology: III. Config: Store config in the environment since env vars are easy to change between deploys without changing any code X.

Continue reading 

When you host your project code on GitHub and want to release it as a docker image for deployment or just publish it, the way to go are GitHub actions. Actions are basically hooks that can start CI/DC workflows on repository events. GitHub actions can be used to build and push images to GitHub’s Container Registry which are reachable under https://ghcr.io which is part of the package registry. The package registry is not only for docker images, it can also host quite a few other kinds of packages.

Continue reading 

I started this blog in March 2013 when I was working for ImagineEasy when I had a few ideas to write down on how I’d work with Doctrine Repositories. I still like the idea, but I’d probably do it a bit different today. The blog and also how I’d work with doctrine. At the time Jekyll was the way to handle a static file blog. Since then, again, a few things have changed.

Continue reading 