mirror of
https://github.com/DarkflameUniverse/DarkflameServer.git
synced 2026-10-02 02:43:44 +00:00
109a936798
With new binaries in place, master moves everything onto them while the server keeps running (the dashboard's Live update, /liveupdate or SIGUSR2 to master): - database migrations of the new build first; a failure stops there - UGC finishes the jobs it is running (queued rows stay pending), auth restarts, chat hands its teams to master for the next chat server; master starts the new processes and retries ones that don't come back - once the new chat server is up (CHAT_SERVER_READY) every world connects at once and sends its players again (LoginSessionNotify resync, no login logged) - every world instance is replaced with an instance migration: public worlds and private ones (same password) at once, properties after the old instance saved and froze the property (MIGRATE_PREPARE: no building, claiming or saving there any more), activity zones and character select once their players left or after a wait; empty instances just stop, zones in prestart_worlds get a new one first - the dashboard restarts last and picks the status up again Players land where they stood (position carried in CarriedPlayerState, also on properties and Moon Base). Draining instances get no new players (InstanceMigration::AcceptsNewPlayers) and show as "Moving players" in the world list. The order lives in LiveUpdateMachine.h without master state and is unit tested; master's glue is LiveUpdateCoordinator. Master itself is not replaced. Message IDs are appended only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
22 lines
573 B
C++
22 lines
573 B
C++
#pragma once
|
|
|
|
#include "json.hpp"
|
|
|
|
struct LiveUpdateStatus;
|
|
|
|
/**
|
|
* The dashboard's "Live update" (docs/LiveUpdate.md): starts one on master and shows how it goes. The status comes
|
|
* from master (LIVE_UPDATE_STATUS) and is pushed to browsers on the live_update socket topic.
|
|
*/
|
|
namespace LiveUpdateRoutes {
|
|
void RegisterRoutes();
|
|
|
|
// Master sent a status
|
|
void HandleStatus(const LiveUpdateStatus& status);
|
|
|
|
// Main loop: ask master for the status once connected (a restarted dashboard picks a running update up again)
|
|
void Update();
|
|
|
|
nlohmann::json StatusJson();
|
|
}
|