You are here

UPGRADE.txt in Hostmaster (Aegir) 5.x

-*-rst-*-

This document is formatted using the ReST syntax.

Aegir 0.2 upgrade instructions
==============================

This document describes briefly how to upgrade existing Aegir
platforms.

Upgrading the Drupal core safely
--------------------------------

If you want to use provision to upgrade your Aegir installation, you
can, but it's a bit more tricky than a usual site because you cannot
(yet) use the regular frontend to do that. The first step is to
import and verify the "default" site so it has a proper
configuration. Then it can be migrated to a new platform.

Shell commands::
 cd /var/aegir
 ./drush/drush.php dl drupal-5.17
 cd drupal-5.17
 cvs co -d profiles/hostmaster contributions/profiles/hostmaster
 cvs co -d profiles/hostmaster/modules/hosting contributions/modules/hosting
 cvs co -d profiles/hostmaster/themes/eldir contributions/themes/eldir
 # also checkout any modules you may have enabled in the d5 platform
 # now you want to add the platform in the frontend (Create content -> platform) and wait for the task to be processed
 cd ../drupal-5.x
 /var/aegir/drush/drush.php --verbose=2 provision verify
 /var/aegir/drush/drush.php --verbose=2 provision import default
 /var/aegir/drush/drush.php --verbose=2 provision verify default
 /var/aegir/drush/drush.php --verbose=2 provision backup default ~/default.tar.gz
 cd ../drupal-5.17
 /var/aegir/drush/drush.php --verbose=2 provision verify
 /var/aegir/drush/drush.php --verbose=2 provision deploy d6.aegir.example.com ~/default.tar.gz
 # review changes, see if it works to your liking, when you're done:
 /var/aegir/drush/drush.php --verbose=2 provision deploy aegir.example.com ~/default.tar.gz
 /var/aegir/drush/drush.php --verbose=2 provision delete d6.aegir.example.com
 crontab -e # change root to new platform, make sure you have a --uri=aegir.example.com

Note that the import/verify of the 'default' site is required only
because that site is typically ignored in Aegir. This procedure will
migrate your main frontend away from that 'default' setup. See
http://drupal.org/node/453540 for details.

Upgrading Hostmaster from 0.1
-----------------------------

Upgrading hostmaster should be as simple as removing the provision and
drush modules from your profiles/hostmaster/modules directory. You
also need to create a new drush and provision checkout. Finally, you
can remove the drush.php symlink.

You will also need to update the hosting module and run update.php so
that new changes to the database are taken into account. This will
trigger platform verification and other cleanup tasks. Starting with
0.2, this process will be automated (see the above process).

Finally, you will need to put the path to that new drush in the
webserver node configuration. Rerunning the wizard will prompt you for
that. Make sure you also run the hosting setup command.

Shell commands::
 export CVSROOT=:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal
 cd /var/aegir
 cvs co -d drush  contributions/modules/drush
 mkdir .drush
 cvs co -d .drush/provision  contributions/modules/provision
 rm drupal-5.x/drush.php
 rm -r drupal-5.x/profiles/hostmaster/modules/provision
 rm -r drupal-5.x/profiles/hostmaster/modules/drush
 cvs up -A drupal-5.x/profiles/hostmaster/modules/hosting
 # here run update.php on the site and setup your drush path
 cd drupal-5.x && ../drush/drush.php hosting setup

The above commands need to be ran as your "aegir" user, especially the
last step.

Upgrading Hostslave platforms from 0.1
--------------------------------------

Provision has been migrated out of the platforms. It used to be
installed in the profiles/hostslave/modules directory. It is now in
~/.drush/provision. So you can simply cleanup the hostslave profile
and the virtual host created for the hostslave profile. You can also
remove the drush symlink.

Shell commands::
 cd /var/aegir
 rm -r drupal-6.x/profiles/hostslave
 rm config/vhost.d/hostslave
 rm drupal-6.x/drush.php

You should also delete the database created during the hostslave
install:

SQL commands::
 DROP DATABASE hostslave;

File

UPGRADE.txt
View source
  1. -*-rst-*-
  2. This document is formatted using the ReST syntax.
  3. Aegir 0.2 upgrade instructions
  4. ==============================
  5. This document describes briefly how to upgrade existing Aegir
  6. platforms.
  7. Upgrading the Drupal core safely
  8. --------------------------------
  9. If you want to use provision to upgrade your Aegir installation, you
  10. can, but it's a bit more tricky than a usual site because you cannot
  11. (yet) use the regular frontend to do that. The first step is to
  12. import and verify the "default" site so it has a proper
  13. configuration. Then it can be migrated to a new platform.
  14. Shell commands::
  15. cd /var/aegir
  16. ./drush/drush.php dl drupal-5.17
  17. cd drupal-5.17
  18. cvs co -d profiles/hostmaster contributions/profiles/hostmaster
  19. cvs co -d profiles/hostmaster/modules/hosting contributions/modules/hosting
  20. cvs co -d profiles/hostmaster/themes/eldir contributions/themes/eldir
  21. # also checkout any modules you may have enabled in the d5 platform
  22. # now you want to add the platform in the frontend (Create content -> platform) and wait for the task to be processed
  23. cd ../drupal-5.x
  24. /var/aegir/drush/drush.php --verbose=2 provision verify
  25. /var/aegir/drush/drush.php --verbose=2 provision import default
  26. /var/aegir/drush/drush.php --verbose=2 provision verify default
  27. /var/aegir/drush/drush.php --verbose=2 provision backup default ~/default.tar.gz
  28. cd ../drupal-5.17
  29. /var/aegir/drush/drush.php --verbose=2 provision verify
  30. /var/aegir/drush/drush.php --verbose=2 provision deploy d6.aegir.example.com ~/default.tar.gz
  31. # review changes, see if it works to your liking, when you're done:
  32. /var/aegir/drush/drush.php --verbose=2 provision deploy aegir.example.com ~/default.tar.gz
  33. /var/aegir/drush/drush.php --verbose=2 provision delete d6.aegir.example.com
  34. crontab -e # change root to new platform, make sure you have a --uri=aegir.example.com
  35. Note that the import/verify of the 'default' site is required only
  36. because that site is typically ignored in Aegir. This procedure will
  37. migrate your main frontend away from that 'default' setup. See
  38. http://drupal.org/node/453540 for details.
  39. Upgrading Hostmaster from 0.1
  40. -----------------------------
  41. Upgrading hostmaster should be as simple as removing the provision and
  42. drush modules from your profiles/hostmaster/modules directory. You
  43. also need to create a new drush and provision checkout. Finally, you
  44. can remove the drush.php symlink.
  45. You will also need to update the hosting module and run update.php so
  46. that new changes to the database are taken into account. This will
  47. trigger platform verification and other cleanup tasks. Starting with
  48. 0.2, this process will be automated (see the above process).
  49. Finally, you will need to put the path to that new drush in the
  50. webserver node configuration. Rerunning the wizard will prompt you for
  51. that. Make sure you also run the hosting setup command.
  52. Shell commands::
  53. export CVSROOT=:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal
  54. cd /var/aegir
  55. cvs co -d drush contributions/modules/drush
  56. mkdir .drush
  57. cvs co -d .drush/provision contributions/modules/provision
  58. rm drupal-5.x/drush.php
  59. rm -r drupal-5.x/profiles/hostmaster/modules/provision
  60. rm -r drupal-5.x/profiles/hostmaster/modules/drush
  61. cvs up -A drupal-5.x/profiles/hostmaster/modules/hosting
  62. # here run update.php on the site and setup your drush path
  63. cd drupal-5.x && ../drush/drush.php hosting setup
  64. The above commands need to be ran as your "aegir" user, especially the
  65. last step.
  66. Upgrading Hostslave platforms from 0.1
  67. --------------------------------------
  68. Provision has been migrated out of the platforms. It used to be
  69. installed in the profiles/hostslave/modules directory. It is now in
  70. ~/.drush/provision. So you can simply cleanup the hostslave profile
  71. and the virtual host created for the hostslave profile. You can also
  72. remove the drush symlink.
  73. Shell commands::
  74. cd /var/aegir
  75. rm -r drupal-6.x/profiles/hostslave
  76. rm config/vhost.d/hostslave
  77. rm drupal-6.x/drush.php
  78. You should also delete the database created during the hostslave
  79. install:
  80. SQL commands::
  81. DROP DATABASE hostslave;