Wiki Transfer

Template:MARKDOWN 1. Check `favog` is up well in advance. If it isn't, get Matt to start it 1. Make sure Matt is available when you're planning to make the switch 1. 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. 1. On merple, as root, run `~/server_synch` and make yourself comfortable. It takes a significant length of time 1. Get Matt to deploy the offline version of the website to favog 1. Get Matt to swap http/https over to `favog` on the router - leave ssh until you have confirmed everything is working 1. 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 1. Check it all

   1. Check the website is up.
   1. Check the wikis are up
   1. Check the wikis are editable
   1. Check ls2 is running and that you can search for a recent page (favog:~ # systemctl status ls2)

1. Get Matt to swap ssh over 1. Check ssh now connects to `favog`

1. 1. 1. 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 1. Make sure Matt is available when you're planning to make the switch 1. Ensure the Plot team are warned via discord 1. Remind Matt before you start 1. Tell Plot you are starting via discord 1. 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 1. 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

1. On favog, as root ```bash systemctl stop mariadb systemctl stop jetty systemctl stop apache2 ``` 1. On merple, as root ```bash 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 ``` 1. On favog, as root

   1.

```bash systemctl start mariadb systemctl start jetty systemctl start apache2 /etc/cron.daily/ls2-build ``` 1. Get Matt to swap http/https over to `favog` on the router - leave ssh until you have confirmed everything is working 1. 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 1. Check it all

   1. Check the website is up.
   1. Check the wikis are up
   1. Check the wikis are editable
   1. Check ls2 is running and that you can search for a recent page

1. Get Matt to swap ssh over 1. Check ssh now connects to `favog` 1. Tell Plot the maintenance is complete via discord