The website, Discord bot and background jobs now share a central PostgreSQL data store. This puts the foundation for public features and regularly updated analyses in one place. The migration was not carried out in one go: it was prepared in stages, compared in parallel and then completed in a controlled manner.
A shared foundation
Player, clan, ship and ranking data continues to be updated automatically. Ship meta data, rankings, snapshots and sitemaps also remain part of ongoing background processing. These tasks are still divided into separate jobs, but now use the same central data store.
The API cache, short links, and bot and server configurations are also held centrally in PostgreSQL. The website and Discord bot can therefore access the data intended for them without changing existing features or update processes for users.
Checked in a controlled manner
The main areas were checked before and after the switchover. These included website pages, bot features, notifications, automatic updates, short links and sitemaps. The key question was not simply whether individual pages were reachable, but whether the interconnected features continued to work together as intended.
The fallback state is retained
The previously used SQLite databases were not removed immediately. They are temporarily retained as a frozen fallback state, but are no longer the active data source. This clearly separates the state kept only for recovery from the data store used in ongoing operation.
For visitors and bot users, operation stays the same. The change mainly concerns the shared technical foundation behind the existing pages, analyses and Discord features.