Wiki Transfer

Latest revision as of 19:47, 10 June 2026

Check merple is up well in advance. If it isn't, get Matt to start it
Build the offline version of the website
On gonzo, as root, run `~/server_synch` and make yourself comfortable. It takes a significant length of time
Deploy the offline version of the website to merple
Swap http/https over to `merple` on the router - leave ssh until you have confirmed everything is working
Check it all
1. Check the website is up.
2. Check the wikis are up
3. Check the wikis are editable
Get Matt to swap ssh over
Check ssh now connects to `merple`

@@ Line 1: / Line 1: @@
 [[Category:IT]]
-# Check favog is up well in advance. If it isn't, get Matt to start it
+# Check merple is up well in advance. If it isn't, get Matt to start it
-# Make sure Matt is available when you're planning to make the switch
+# Build the offline version of the website
-# 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.
-# Get Matt to build the offline version of the website
 # On gonzo, as root, run `~/server_synch` and make yourself comfortable. It takes a significant length of time
-# Get Matt to deploy the offline version of the website to favog
+# Deploy the offline version of the website to merple
-# Get Matt to swap http/https over to `favog` on the router - leave ssh until you have confirmed everything is working
+# Swap http/https over to `merple` on the router - leave ssh until you have confirmed everything is working
 # Check it all
 ## Check the website is up.
@@ Line 13: / Line 11: @@
 ## Check the wikis are editable
 # Get Matt to swap ssh over
-# Check ssh now connects to `favog`
+# Check ssh now connects to `merple`