Migrating a non-swarm TGS installation to swarm mode

[Cyberboss]

1. Stop TGS (Substeps can be ignored if you don't have DreamDaemon running)

• Linux:
  • Host watchdog version >=5.13.0. (This deviates from your TGS version after updates! Check the version of Tgstation.Server.Host.Service.exe)
    • 1: kill -SIGUSR2 the dotnet executable instance with the command line containing Tgstation.Server.Host.Console.dll. (This is the main systemd PID)
    • 2: Issue a TGS restart through the HTTP API.
  • Host watchdog version <5.13.0
    • 1: kill -9 the dotnet executable instance with the command line containing Tgstation.Server.Host.Console.dll. (This is the main systemd PID)
• Windows
  • Service
    • Host watchdog version >=5.13.0. (This deviates from your TGS version after updates! Check the version of Tgstation.Server.Host.Service.exe)
      • 1: Issue service command 130 to the tgstation-server service to get it to stop and detach (You can do this through the Services control panel).
    • Host watchdog version <5.13.0
      • 1: Kill the Tgstation.Server.Host.Service.exe process.
      • 2: Issue a TGS restart through the HTTP API.
  • Console
    • 1: Kill the dotnet.exe executable instance with the command line containing Tgstation.Server.Host.Console.dll or Tgstation.Server.Host.Console.exe whichever is running.
    • 2: Issue a TGS restart through the HTTP API.

2. Update appsettings.Production with swarm settings for existing server.
3. Update all existing DB instances, setting the SwarmIdentifer column to the migrated server's new Swarm:Identifier configuration setting.
4. Configure other remaining swarm servers and start TGS again. Remember, exactly one node of the swarm must be designated as the controller, all other nodes must have it's address as the ControllerAddress (for inter-server communication), and all nodes must have an Identifier and Address (for inter-server communication) set and the same PrivateKey. Refer to the README.md for full documentation on the swarm system.