Since migrating to my Windows 10 & WSL2 setup a few years ago, I regularly try to reclaim disk space from my WSL2 setup by following the steps outlined in Scott Hanselman's blog post. However, this time it did not work as expected.
For a few of our customer projects, we use Tideways to spot performance bottlenecks and get real-time error detection alerts.
As a bonus, Tideways can track deployment events to compare performance and failure rates before and after the deployment.
Internally we develop our own tools, that we use as CLI. To make it easier to distribute and use them, we create standalone binaries. But often the files are huge.
So let's see how we can make them smaller without losing any functionality.
In the last few days, I was fighting hard to understand and fix an error that occurred when trying to deploy a Magento upgrade in production for one of our merchants.
During the setup:di:compile phase our CI pipeline crashed with the error Undefined array key "instance" in ArgumentsResolver.php on line 171.
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.
Not being happy with our current Docker build process in one of our projects, I was researching how to optimize the process.
Vor Rund einem Jahr war ich zum ersten Mal bei einem DevOps Camp in Nürnberg. In einem Jahr finden zwei solcher Veranstaltungen statt, einmal das "große" Camp mit über zwei Session-Tage im Frühjahr und das DevOps Camp compact mit einem Session-Tag im Herbst. Typisch für ein Barcamp ist die Planung der Themen und der Session-Ablauf, diese werden erst vor Ort von den Teilnehmern genau definiert.