In part one of this series, we covered how you could limit deployments to Platform.sh only when a tag is pushed/created, focusing primarily on using GitHub and the GitHub Actions platform to accomplish this goal. But we’re a polyglot PaaS and strive to be agnostic in our users’ source code management terms of the service. With that in mind, let’s look at how we can accomplish the same goal using GitLab and your CI/CD system. Just like last time, there are some assumptions to consider.

Patch management software automatically applies updates to software, firmware, and other system components. Patching makes sure resources are up to date with the latest security and performance improvements to keep software protected and performing as expected.

In this post, we’ll embark on the journey of building a simple PHP single-page application that interacts with a MySQL database. We’ll integrate logging functionality on top of our application. Logging is a crucial aspect of any application—for providing insights into user behavior, tracking errors, and monitoring performance. We’ll start by walking through how to set up our application.

When cloud service providers first started popping up, many developers were “wowed” by being able to spin up and scale all kinds of infrastructure to deploy their web applications on demand. However, big-box cloud service providers are often complex to use, scaling out is expensive and default monitoring solutions are not very insightful. Besides, we are spoiled developers, and we expect things to be easy.

Digital experience monitoring (DEM) involves tracking the entire digital user journey of your applications, websites, APIs, and other digital services. It focuses on tracking the performance of your web application from the end user’s perspective, offering in-depth insights on user experience, app performance, and customer satisfaction.