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`