Accueil / Taxonomy term

acquia drupal planet

Drupal 8 Configuration Workflows using Git

This blog post is a textual representation of the video shared yesterday. If you are visual learner, watch it. If you are in a hurry, read this blog :). Peter's video also shows how configuration_log module can be used to materialize all config changes in Prod so they may be easily integrated back into the codebase. That is not covered here.

Moving Your Drupal 8 Configuration from Local to Server and Back

Update: a textual representation of the first half of this video has been posted.

Two weeks ago I had a great opportunity to spend a few days working with Moshe Weitzman (moshe weitzman), Justin Randell (beejeebus), Alex Bronstein (effulgentsia), and Stéphane Corlosquet (scor) to look at the challenges and best practices for using the new Drupal 8 configuration system (a.k.a. CMI) to move changes between a local development environment and one or more server environments. We developed ideas, considered new modules for Drupal 8, and tried to figure out if there were any changes to Drupal 8 core that would be needed to make the system better for developers.

One outcome of this was two new modules Configuration log and Configuration Read-only mode. These were written to help demonstrate the capabilities of the new configuration system and enabled us to implement key elements of possible new configuration staging and management workflows. An additional outcome was a number of enhancements by Moshe to the latest version of Drush to facilitate the import and export of configuration.

The screencast video below walks through the process of moving configuration from a local development version of a site, up to a development environment on a server and then to a "live" environment using Acquia Cloud Free. The "live" environment was detected in settings.php and that logic triggered the Configuration Read-only mode module to prevent any configuration changes in the administrative forms. We also used a Cloud Hook to automatically import new configuration when a new git tag was deployed to the "live" environment.

Ryan Weaver and Jeffrey A. McGuire compare notes on Open Source

Ryan Weaver is the single biggest contributor to the Symfony2 framework's documentation (which is excellent, check it out!), a self-described Symfony evangelist, and lead at KnpUniversity.com, makers of fantastic PHP tutorial screencasts like this one on using Composer to include PHP libraries in Drupal 7.

5 Mistakes to Avoid on your Drupal Website - Number 3: Performance

Performance is crucial for providing a great user experience. If the site is slow or balky, even great functionality won’t keep the site visitor engaged.

Don’t wait to migrate. Drupal continuous migration

Whether you are just moving to Drupal or upgrading to a new version of Drupal, if you are starting with an existing website, you are facing the same problem: Your migration timeline. It will take you significant effort to move everything you have to the new system and you cannot play catch-up all the time. That’s why many people are opting for continuous migration. What does that mean? Run the migration project in parallel to your existing website effort and migrate gradually, page by page and URL by URL.

Everything you need to know about naming your Drupal contributed project

So you're contributing a module or theme to the greater Drupal community. Awesome! We're thrilled that you're sharing your work.

Naming your project may be one of the last things on your mind, but a poor naming choice could cause you issues down the road. Your project name ends up in a lot of places, including: Google Search Results, Drupal.org related project listings, the URL to the project, the title of your project page, Drush commands, the filenames of your project files, hook invocations in your project, and CSS classes, to name a few. A name that's used inconsistently can be confusing for users and cause integration issues.

There are several principles to consider and some are more important than others, so I've broken them into three categories: The Essentials, Strong Recommendations, and Further Suggestions.

5 Mistakes to Avoid on your Drupal Website - Number 2: Security

Good security practices protect your site from hacker attacks. In this article we'll look at some methods for reducing security risks on your site. 

Drupal Security Best Practices

Drupal has good security built in if used correctly. However, once you begin to configure your site you might introduce new security issues. Plan configuration so that only trusted users have permissions that involve security risks.

Ruben Teijeiro explains why Drupal is easy

This week's podcast is parts of a fun conversation I had with Ruben Teijeiro at Drupal Camp Vienna in December 2013. I "borrowed" him from mentoring Manuela Hutter at the code sprint to talk with me, but in the end, they both still managed to get a lot done that weekend. Thanks for your contributions, folks!

5 Mistakes to Avoid on your Drupal Website - Number 1: Architecture

Drupal is one of the most flexible content management systems in existence. In this blog series, I'll go over five mistakes to avoid on your Drupal website which include: architecture, security, performance, infrastructure, and website lifecycle management.

Hat tip to my colleague Ryan MacInnis for prompting me to write this up!

From an architecture standpoint, these are the most vital decisions you'll make to ensure the success and performance of your Drupal website.

Pages