Wiki Transfer

1. Check favog is up well in advance. If it isn't, get Matt to start it
2. Make sure Matt is available when you're planning to make the switch
3. If you are planning to allow people to edit the wiki on favog, ask yourself if you really want to do that. If you do, ask Clive what to do. We don't do this any more because it takes forever to synch back to merple over 4G in a field.
4. On merple, as root, run ~/server_synch and make yourself comfortable. It takes a significant length of time
5. Get Matt to deploy the offline version of the website to favog
6. Get Matt to swap http/https over to favog on the router - leave ssh until you have confirmed everything is working
7. If Matt is not leaving more or less immediately, remind him to change beaker's DNS to point the CNAME live at favog instead of merple (www, crew, etc all CNAME to live) so he sees the same website as the public - if you're doing this Matt, you need to do this before checking the sites or get somebody outside the office to check
8. Check it all
   1. Check the website is up.
   2. Check the wikis are up
   3. Check the wikis are editable
   4. Check ls2 is running and that you can search for a recent page (favog:~ # systemctl status ls2)
9. Get Matt to swap ssh over
10. Check ssh now connects to favog

These are the old instructions, kept here so I have them if the new instructions don't work. please ignore

1. Check favog is up well in advance. If it isn't, get Matt to start it
2. Make sure Matt is available when you're planning to make the switch
3. Ensure the Plot team are warned via discord
4. Remind Matt before you start
5. Tell Plot you are starting via discord
6. It's probably easier to have two windows open, one on each server, but if you do be very sure which server you are running each command on
7. On each server, as root
   1. Edit /etc/mediawiki_global.inc.php - ensure $wgReadOnly is set if the server is to be read-only, ensure it is not set if the server is to be editable
8. On favog, as root

   systemctl stop mariadb
   systemctl stop jetty
   systemctl stop apache2

9. On merple, as root

   systemctl stop mariadb
   systemctl stop jetty
   systemctl stop apache2
   rsync -avz --progress --partial-dir=.rsync-partial --delete /srv/www/htdocs favog:/srv/www/ --exclude mediawiki-public-images --exclude mediawiki-crew-empire-images
   rsync  -avz --progress --partial-dir=.rsync-partial --delete /var/lib/mysql/* favog:/var/lib/mysql/
   rsync  -avz --progress --partial-dir=.rsync-partial --delete /srv/www/htdocs/mediawiki-public-images favog:/home/websites/ --delete-excluded --exclude=pdf-book*
   rsync  -avz --progress --partial-dir=.rsync-partial --delete /srv/www/htdocs/mediawiki-crew-empire-images favog:/home/websites/
   rsync  -avz --progress --partial-dir=.rsync-partial --delete /etc/apache2/ssl.* favog:/etc/apache2/
   systemctl start mariadb
   systemctl start jetty
   systemctl start apache2

10. On favog, as root

    1. systemctl start mariadb
       systemctl start jetty
       systemctl start apache2
       /etc/cron.daily/ls2-build

11. Get Matt to swap http/https over to favog on the router - leave ssh until you have confirmed everything is working
12. If Matt is not leaving more or less immediately, remind him to change beaker's DNS to point the CNAME live at favog instead of merple (www, crew, etc all CNAME to live) so he sees the same website as the public - if you're doing this Matt, you need to do this before checking the sites or get somebody outside the office to check
13. Check it all
    1. Check the website is up.
    2. Check the wikis are up
    3. Check the wikis are editable
    4. Check ls2 is running and that you can search for a recent page
14. Get Matt to swap ssh over
15. Check ssh now connects to favog
16. Tell Plot the maintenance is complete via discord