Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I'm moving all sites to a new Octopus instance (on the same server), to eliminate lingereing issues caused by the original instance being upgraded for the last couple years. Once the final site is moved, what is the correct way to get rid of the old instance, and ensure that the old Nginx vhost entries are deleted, but the MySQL databases are *not* deleted?
Comments
Comment #1
omega8cc CreditAttribution: omega8cc commentedYou can easily take down any instance (for web access) by removing (or moving away) its config symlink you can find in the
/var/aegir/config/server_master/nginx/platform.d/
directory and then reloading Nginx withservice nginx reload
. This is much easier, and allows you to keep the old instance and its config files (vhosts) as a reference, if needed, while totally disabled for web access. Note however that you will need to disable also cron for this old instance, by removing or renaming its cron central script/var/xdrago/run-USER
.Comment #2
omega8cc CreditAttribution: omega8cc commented