Operations

Running an already-deployed Splintertree cluster — admin portal, monitoring, the operator surface.

For bringing the cluster up in the first place, head to Getting started › Deployment.

Educational deployments only

Splintertree does not recommend running public realms with this code. The Operations section documents the cluster's operational surface so readers can study it and so contributors can run a full topology on their own machines — not as guidance for production hosting. The project ships no Blizzard data and operates no public servers.

• Monitoring — Prometheus, Grafana, log routing.

Operating the cluster

The admin portal under splintertree-web-frontend (~80 pages) is the day-to-day operator UI:

• Per-realm CRUD for accounts, characters, guilds, items, quests, creatures, gameobjects, maps, spells, achievements, battlegrounds, dungeons, currencies, factions, talents, world events, races, classes.
• Tickets, anti-cheat (Warden), player reports, bans.
• Mods, addons, patches, realm pools, bots, calendar, world-config tunables, scripts, NPC AI / personality.

There is no SOAP and no raw SQL dives required to operate a realm. The admin REST API at splintertree-web-api exposes every operation as a JSON endpoint.

DB-driven gameplay constants

Tunables live in world.world_config and the admin UI auto-renders them as typed forms. Operators change balance without redeploying; schema changes ship through mods.

Live DBC re-assembly

Edits in the admin UI re-pack into the launcher's next patch sync. Implementation: splintertree-web-api/src/dbc_export.rs.