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.
I have to admit, I am not the best at editing neon configuration files. I regularly mess that up and then things break. How to fix that? Well, why not lint those files in the CI pipeline?
In a few projects, we sometimes had the problem, that invalid JSON files were provided by the customer and not checked for errors. To prevent this, we searched for the smallest possible solution.
Yesterday, I was running into an issue while trying to register a new GitLab CI Runner with our self-hosted GitLab instance. While that worked fine about 2 weeks ago, it did not this time. The only difference is, that we recently upgraded to version 15.9.2 of GitLab.
We've covered the basics of our Docusaurus CI setup already in another blog post. In this blog post, we'll show you how to the build pipeline to lint the nginx configuration used in our Docusaurus setup.
Recently, I wanted to improve our CI build pipelines with some custom-built Docker images for our PHP projects. To make sure I can reuse the image in as many of our projects as possible, I wanted to compile and install as many PHP extensions as possible.
It's been a few months sine we migrated from Silverstripe to Docusaurus for our blog. Quite a few blog posts have been published since then via the CI pipeline we've set up. This blog post covers how we do things.
For a client, we also handle the vulnerability management of the projects. This also involves manual checks after a new project is launched, to ensure that no critical security problem is caused by misconfiguration.