Building a site with a custom Drupal install profile using Pantheon and Terminus

Image

We are always thrilled when our friends and partners tell people how they are using the Pantheon platform. Such is the case with 4Site up in Washington, DC. 

A while back John Shortess, Director of Technology at 4Site, wrote an article describing how they use Drupal, Pantheon One and our open source cli tool, Terminus, in building out great websites for their clients.   Shortess gives a short introduction to the problem that Terminus helps them solve and then gives away their bash script for provisioning custom installs.

We’re big fans of Pantheon here at 4Site Studios. Even if a client site doesn’t end up being hosted there for whatever reason, we’ll probably still develop the site on Pantheon because their development tools fit very nicely into our small team’s workflow. The biggest pain point we’ve had was with the initial site provisioning, since we develop most of our sites using a custom install profile,4Site Hub. Custom start states are available as part of the Pantheon One (formerly Zeus) package, but most of our clients don’t have pockets that deep. So I developed a kludgy workaround involving Drush make and importing the resulting tarball through the Pantheon dashboard.

Terminus is a great tool and we are glad to see our partners and friends using it to automat things and make their lives easier. Now that we support WordPress as well as Drupal, Terminus is evolving. We have a new github repo that contains the version that works with both, pantheon-systems/cli. Going forward, this will be our primary tool. Download it and kick the tires. Let us know what you think.

Cheers!
=C=