Composer has helped quite a lot in the area of installation and dependency management for Drupal and Drush; however, users who want to get a quick start with Drush are sometimes put off by the Composer-based install. As of the Drush 8.0.0-rc3 release, it is now possible to install Drush using a phar. This requires fewer steps than the previous method.
[Related] Applying Updates to Drupal Core on Patheon with Drush
Pantheon is pleased to bring Drush 10 to the platform. Drush 10 is the latest version of the venerable command line tool that has been helping streamline Drupal tasks for well over a decade. If you’re new to Drush, there are a lot of things you can do with it, from one-off cache clears to scripting configuration management as part of continuous integration. Even if you don’t use Drush, you may find it interesting to know that Pantheon relies on it behind-the-scenes for several workflow operations.
Our idea of delivering Drupal as a service is starting to catch on as people realize just what it could mean for the project’s ability to expand. But the notion of “SaaSifying” open-source tools isn’t new, and actually we think the traditional model is kind of broken.
We get questions almost every day about Drupal multisite. In our experience, Drupal multisite does not meet the needs of organizations looking for a successful technology solution to manage dozens/hundreds/thousands of websites.
For anyone new to the terminology, a multisite is where you set Drupal up to connect to different databases depending on the incoming url, which allows one instance of Drupal to serve different sites under different domain names.
If content management systems were toys, Drupal would be Lego. It’s infinitely customizable. If you can dream it, you can build it. The one downside? You have to put it together brick by brick.
Drupal can be an ideal CMS for university websites. In addition to the customizability, it excels at managing complex content ecosystems. Content like, say, a main university page with dozens of department pages, student life pages, all with multiple content types interacting in multiple ways.
In my last blog post about migrating to Drupal 8, I focused on setting up a connection to your source Drupal 6 or 7 database. The drush migrate-upgrade command takes the credentials for your source database and configures migrations that can be run separately. With the database alone, you can move all of your Drupal nodes, users, taxonomy terms and other information held in the database.
I believe that the web is Earth’s most powerful communication tool. In particular I believe in the Open Web, a place of small pieces loosely joined, true to the original architecture of the internet, the philosophy of UNIX, and of HTTP as a protocol. This technology is rewriting the way humanity operates, and I believe it is one of the most positive things to emerge from the 20th century.
Irina Zaks is a Drupal instructor at Stanford University and the co-founder of Fibonacci Web Studio, a company focused on developing advanced web solutions for research and academia. This is the second post of a two-part series on choosing to move to Drupal 8/9, and creative ways to make the migration feasible.
Irina Zaks is a Drupal instructor at Stanford University and the co-founder of Fibonacci Web Studio, a company focused on developing advanced web solutions for research and academia. This is the first post of a two-part series on choosing to move to Drupal 8/9, and creative ways to make the migration feasible.
As many of you know, Drupal 6 reached End-of-Life on February 24, 2016, meaning it no longer receives security updates from Drupal.org.
At Pantheon, we are committed to helping our customers operate their Drupal 6 sites for as long as they are needed. Pantheon will continue hosting and supporting existing Drupal 6 sites on our platform.