Automatic background updates for Drupal core on Drupion servers

While Drupal community is still deciding on implementing automatic background updates (https://www.drupal.org/node/2367319 and https://www.drupal.org/node/606592) similar to WordPress' Automatic Background Updates feature, Drupion customers have already been enjoying automatic Drupal core security updates for already several years.

After receiving number of requests from Drupion customers not to limit such automatic updates to only security releases, we are proudly announcing we have introduced changes to our platform, so it takes care of all Drupal core updates within the first hours such updates are rolled out by Drupal project.

The core update process takes backup of the file system and database for each website before executing, so if anything goes awry then Drupal websites can be easily reverted to their last state. The Drupal core update process also protects the .htaccess and robots.txt files and restores them thereafter. Custom profiles won't be touched by core updates, so they are fine to modify.

At the present all Drupal websites are included by default. So if you have Drupal websites with patched or modified cores, then please login to your profile account at https://dashboard.drupion.com and let us know which websites to exclude and we will do it right away. However, in the near future we will push a new option for opting websites out or in the Drupal core update process via control panel's UI.

Update: Please read the new announcement on this.

Comments

Sam Moore's picture

Just saw your newsletter about the automated core updates. While I think this is basically a good thing, I have some concerns.

  • While I don't patch core, I do have mods to some of my .htaccess files, and some of my dev sites have robots.txt set to exclude them from indexing. Will you be protecting and restoring these files during the core update process?
  • One of my sites runs a profile, which can be tricky to update. If that site is broken by an automated update, it's going to cause significant problems. Your newsletter mentioned a way to exclude a site from the auto-update procedure, but I'm not sure how to do that?
  • Would you consider notifying server admins of these updates, preferably in advance, so we can schedule user testing?

Thanks

Alex Shapka's picture

Dear Sam,

I've just made an addition to the announcement:

The core update process takes backup of the file system and database for each website before executing, so if anything goes awry then Drupal websites can be easily reverted to their last state. The Drupal core update process also protects the .htaccess and robots.txt files and restores them thereafter. Custom profiles won't be touched by core updates, so they are fine to modify.

At the present all Drupal websites are included by default. So if you have Drupal websites with patched or modified cores, then please login to your profile account at https://dashboard.drupion.com and let us know which websites to exclude and we will do it right away. However, in the near future we will push a new option for opting websites out or in the Drupal core update process via control panel's UI.

I hope this answers your questions.

Sam Moore's picture

Hi Alex - thanks for your thoughtful response.

Maybe you could automate a notice to the site contact that the update has happened?

Patrick Branwell's picture

Maybe you could automate a notice to the site contact that the update has happened?

This feature request has been implemented on the latest release of Drupal core updates, which we already pushed to all servers.

Add new comment