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.
I’m thrilled to announce Pantheon is now offering Managed Updates for both WordPress and Drupal. This release has been nearly a year in the making, and stems directly from our strategic acquisition of StagingPilot last May.
DrupalCon LA was a complete blast. In addition to exciting announcements, amazing sessions and tons of fun side events, there were also a lot of super productive sprints that really pushed Drupal development forward. In the Drush sprints, the remaining issues tagged for Drush 7 were all reviewed, and either resolved or deferred, cumulating in the release of Drush 7.0 Stable today.
If you’ve spent much time upgrading older websites to PHP 7, it’s likely you have encountered the annoying situation where PHP notices are printed directly into the HTML output, causing them to display in an ugly, unformatted jumble at the top of the page. The effect looks something like this:
WordPress multisite is a great tool to streamline website management while providing site owners with some versatility. At its best, multisite is the perfect solution for managing multiple websites at once.
But, a multisite certainly isn’t a one-size-fits-all solution. There are some caveats. Before we celebrate or dismiss it, let’s take a look at multisite and see what it’s all about.
Teams that build websites and marketing projects are often distributed geographically or across groups. It's common to have multiple internal and external collaborators, whether that's IT, marketing and a vendor, or a small business owner and a few independent contractors. Increasingly, these different players are spread out across the globe.
While working with clients and helping them create awesome websites, we’ve noticed a need for an outgoing static IP. Pantheon’s cloud architecture is awesome—based on Linux containers, it allows us to scale easily, migrate containers, restart them in just seconds without any customer impact, resize them, and so on. The downside of having such great flexibility is not being able to assign a fixed IP address to a container. This is sometimes needed by third-party applications that only accept connections from services they know about.
Editor’s Note: This blog post and conference presentation was written for teams looking to migrate to Drupal 8. The ideas here are just as applicable to teams now looking to migrate to Drupal 9, 10, or 11. The big deal about Drupal 9 is that it is not a significant architectural change, compared its previous version the way Drupal 8 was a significant architectural change to Drupal 7.
Much of my day to day work as an ACE at Pantheon is spent confirming that certain development workflow tasks are possible on the platform. Lately, my preferred way of showing that something is possible—and stays possible—is by writing an automated test.
In this article, I will be talking in the context of website projects, but the value of dependency management extends to other types of projects, as well.
To understand dependency management, we must first understand dependencies.