#Blt drupal code#

Starts a build container (uses the PHP 7.2 CLI Docker image from Docker Hub).So I built a shell script that does the following: This works great for hosting in Acquia Cloud, Pantheon, or other similar environments, but if you need to deploy your BLT site into a container-only environment like Kubernetes, you need to generate a BLT deployment artifact, then get that into a deployable Docker container.Īlong that theme, my first goal was to make it so I could build the deployment artifact in a perfectly clean environment-no PHP, no Composer, no Node.js, no nothing except for Docker.

#Blt drupal code#

The first problem: BLT has built-in tooling to deploy new code to environments in traditional cloud environments, in a separate Git repository.

Generating a build artifact using only Docker not to mention it would make Kubernetes barf!Īnyways, I figured I'd jump right in and document how I'm doing this, and not get too deep into the whys. Why, yes! And while I use, maintain, and love Drupal VM-even for this particular project, for the main local dev environment-it is just not economical to deploy and maintain a highly-scalable production environment using something like Drupal VM.Yes, Acquia BLT is a great tool to use for building and deploying Drupal to Kubernetes!.And it's not directly tied to Acquia Cloud, so you can use it with any kind of hosting! It has default configurations and packages to help make complex Drupal sites easier to maintain and deploy. It has built-in testing integration with PHPUnit and Behat.

Acquia BLT is not just for Acquia Cloud sites it is a great way to kickstart and supercharge any large-scale Drupal 8 site.

Don't you, like, have to use Docker instead of Drupal VM? And aren't you the maintainer of Drupal VM?.

You can deploy a project built with Acquia BLT to Kubernetes?.

Why are you using Acquia BLT with a project that's not running in Acquia Cloud?.

what? If you're reading the title of this post, and are familiar with Acquia BLT, you might be wondering: