Migrate web servers to new host

[connorhsm]

To migrate existing web servers to new server host ahead of upcoming game update, where the game server host will also move to the same host.

Ideally, set up a new set of web servers a long side of the existing host, but on a new domain. Test and confirm working as expected by accessing the admin pages and other various reports.

Following this, there needs to be a plan to cut over to the new host before migration can complete.

Do we even keep the web servers on the same server as the game?

Current: (DigitalOcean)

• Web servers running on the same machine as game server
• The host machine has a floating IP of 159.89.255.33
• The subdomains play.twohoursonelife.com and web.twohoursonelife.com each direct to the host machine
• All client and server settings correctly direct to web.* when referring to any web servers

Future: (AWS)

• Web servers running on the same machine as game server
  • Future goal is to move these web servers into a container, which could then be migrated to the satellite server aka container host
• The game host machine has an Elastic IP of 44.215.246.168
• The subdomain play.twohoursonelife.com will in future direct to this address (This is scheduled to occur during the upcoming update process)
• Temporary domain for new web servers until cut over point is reached. aws-web.twohoursonelife.com

Plan to setup

• [x] Setup new domain
• [x] Follow any info I can find in OneLifeWeb to setup servers
• [x] Setup OneLifeWeb with temp domain
• [x] Setup OneLifeWeb with production credentials
• [x] Confirm temp OneLifeWeb is working as expected
• [x] Migrate existing version files and photos
• [x] Plan cut over
• [x] Complete cut over

Voila

[connorhsm]

Cut over complete, monitoring DNS and functionality.

Impressive how quickly this happened. Thankful that I adjusted cache times to minimum in preparation.