ConduitDocs

1. The three layers#

LayerWhat it isWhere
Panel + conduitdNext.js dashboard + the reconcile controller. Owns the desired state (conduit.json on the Gluster store), provisions/scales Proxmox LXCs, serves ALL config to servers, and is the HTTP API.panel CTs 190/191/192 behind VIP 10.0.0.50:3001
ConnectorOne jar (conduit-connector.jar), Paper + Velocity in one. Registers each server with the panel, heartbeats players/TPS, applies panel config live (chat, tab, bossbar, packs, redis, sharding, …), executes queued actions, and exposes the Skript bridge (§5).plugins/ of every managed server
Skript overlayThe live Skydinse game content, adopted verbatim where possible, plus conduit-* glue scripts that adapt it to the connector bridge instead of CloudNet/Skyd plugins.plugins/Skript/scripts/ per server; canonical copies in skript/conduit-games/

Config flow: panel store → connector heartbeat (~3s) → connector applies live (most network features need no restart). Files (worlds, plugins, scripts, server.properties) flow at provision/resync via the overlay chain (egg → _global/<kind> → named templates → task).


Edit on GitHubFEATURES.mdUpdated