Building the Pantheon platform meant tackling one of the big remaining “hard problems” in cloud services head-on: how to provide a secure, scalable, synchronous network-attached filesystem for Drupal? We solved this problem with Valhalla, a breakthrough technology that serves files for the 10s of 1,000s of Drupal sites running on Pantheon.

Migrating a WordPress site onto the Pantheon platform is an easy process and can be done with just a few clicks. However, one of the limitations to that import process is the size of the tarball you create.

Today I am extremely proud to announce Pantheon’s Cloud Integration Tools suite, comprised of Quicksilver Platform Hooks, a new release of our Terminus command-line interface, a new YAML-based project configuration interface, and broad compatibility with SAML for centralized authentication.

Editor's Note: This post was written collaboratively by Dharizza Espinach Barahona of Montreal-based Drupal experts at Evolving Web, along with Eric Michalsen of Pantheon. When it was published, Drupal 9 was the newest version of Drupal. Drupal 10 and 11 have since been released but the ideas in this post still hold true.

At DrupalCon New Orleans this month, my co-worker Andrew Taylor and I presented Lessons from WordPress Core.

To keep something safe, you protect it under lock and key, right? Same is true in Drupal and WordPress. Except in these CMSs, that key is unfortunately often hidden under the “Welcome” mat called your database. Not always a very secure place for such important items. So, the question is, what can you do to keep the key safe?

Let’s back up a few steps. Why are there keys and where are they in the first place?