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.

I had the pleasure of returning to DrupalCamp FL (DCFL) again this year and even now in its sixteenth year, DCFL 2024 was as lively and energetic as ever. Approximately 130 people descended upon Florida Technical College to share their experiences and knowledge surrounding Drupal and I’m here to share the highlights!

Throughout the years, many users have asked us if it’s possible to only deploy to Platform.sh when a tag is pushed using a source code integration. The answer is: with our current source integrations, it's not—but that doesn’t mean it’s impossible. Platform.sh is based on Git and because of this, acts as a remote for your code repository.

Managing web applications from the ground up can be a daunting task. One application alone can quickly grow in complexity, let alone the multiple applications that are often required by different business units and stakeholders growing simultaneously. Add the ever-changing landscape of trendy frameworks and runtimes, and you quickly find yourself with an unmanageable mess of different technologies. Standardizing your application stack can help reduce the clutter.