#BLT DRUPAL VM CODE#

Once I have the my/site-name image, I tag it appropriately and-in this case-push it up to a repository I have set up in AWS ECR. In my case, I have a preconfigured PHP base image (based off php:7.2-apache-stretch) which installs extensions like gd, pdo_mysql, simplexml, zip, opcache, etc. Note that this Dockerfile is meant to build from a PHP container image which already has all the required PHP extensions for your project. I put that Dockerfile into my BLT project root, and run docker build -t my/site-name. Here's the Dockerfile I am using to do that: So after we have a deployment artifact in the deploy/ directory, we need to stick that into a Docker container and then push that container into a Docker registry so we can use it as the Image in a Kubernetes Deployment for Drupal.

Building a Docker container with the build artifact That would cut out 3-5 minutes from the build process. Now, I could optimize this build process further by building my own image which already has everything set up so I can just run blt artifact:build, but for now I'm a little lazy and don't want to maintain that.

Runs blt artifact:build to build a deployment artifact in the deploy/ directory.Īll you need is to be in a BLT project directory, and run.

Installs the required dependencies for PHP.

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 VM 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:

Blt drupal vm