Deploying Web stacks DRY-ly with Ansible, Part 2: Users and Logins

In the last part we began by setting up the core infrastructure necessary to stand up a new server using automation and Continuous Integration. A Gitlab instance serves as the repository, with Gitlab CI connecting to the target server to deploy playbooks and execute Ansible. Our playbooks were surprisingly sparse due to the fact we relied on Ansible Roles to do most of the heavy lifting. Now, all we need to do is push code to our infrastructure repository, and CI will configure the server for us.

Deploying Web stacks DRY-ly with Ansible, Part 1: Infrastructure

I've been working on a new site for the last several months. It runs great locally, but when I started thinking of putting it on a live server, I ran into a series of problems. I was hoping that I could simply upgrade my web server from PHP 5.6 to PHP 7, then deploy my Drupal 8 site in place. Sounds simple, right? unfortunately, PHP 7 introduced compatibility-breaking changes which caused problems for my old, Drupal 7-powered site. If I wanted to install both PHP 5.6 and PHP 7 on the same server, I...

Dropwhale 2.0 RC2

For the last few months I've been working on a rewrite of Dropwhale, my Docker-based testing harness for Drupal 8 modules. While I didn't intend to spend most of my weekend on it, I'm pleased with the progress it's made.  The improvements The first, and perhaps biggest change is that it's now based on Nginx and PHP-FPM. I've wanted to switch to Nginx for some time now, but it's been difficult for me to make the transition from Apache. I spent several weekends and evenings teaching myself the...