Fix instructions for upgrading Drupal core

From https://github.com/aegir-project/documentation/issues/22...

@colan commented on Jun 19, 2016:

At http://docs.aegirproject.org/en/3.x/install/upgrade/#the-hostmaster-migrate-command, I added instructions for upgrading Drupal core to a new release if one doesn't want to wait for a new Aegir release (say to avoid security vulnerabilities).

However, it's a dangerous in-place recipe. Now that the changes from https://www.drupal.org/node/2698027 are in, we should update these instructions to use hostmaster-migrate instead. It'll now grab the latest stable Drupal core.

It needs more testing though as only @helmo has confirmed that this works.

@helmo42 commented on Nov 17, 2016:

We can for now add another command to run ... updb (although it's not required for 7.52)

  1. Run database updates
    • drush @hostmaster updatedb

@helmo42 commented on Nov 18, 2016:

Added in f6ab4236

@helmo42 closed this on Oct 4, 2018

@colan commented on Oct 4, 2018:

Shouldn't we switch these instructions to the safer hostmaster-migrate plan, as I mentioned in the description?

@colan reopened this on Oct 4, 2018

@helmo42 commented on Oct 11, 2018:

Feel free to ... but after almost 2 years I got the feeling that this would never get priority.

Edited Oct 07, 2019 by Colan Schwartz
Assignee Loading
Time tracking Loading