For developers managing multiple Drupal projects across different hosting platforms, configuring separate GitHub Actions workflows for each host can be time-consuming and error-prone. This session presents a flexible, dynamic GitHub Actions setup that adapts automatically to various hosting environments, including Pantheon, Acquia, Platform.sh, and more.
We’ll explore how this solution auto-detects the hosting environment and dynamically configures key settings, such as Composer and Node.js build locations, etc. The workflow manages host-specific tasks such as moving the document root for Acquia and PR-triggered MultiDev management for Pantheon.
You will leave with a ready-to-use GitHub Actions template, detailed instructions on how to customize it for your projects, and an understanding of how to use overrides to fit specific host and site needs. We’ll also explore handling Drupal settings per environment, avoiding unnecessary local rebuilds, and how this workflow simplifies deployments, saving teams time and effort.
