Servers
A server in Dylaris is a managed Docker container with persistent storage, a port, and a lifecycle. You never touch Docker yourself.
Creating one
From the panel: pick a node, give it a name, set RAM and disk, then choose what to run. You can start from
- a Minecraft version and loader (Vanilla, Paper, Fabric, Forge, ...),
- a modpack deployed directly as a runnable server, or
- an existing world you upload afterwards.
A new server goes through pending_setup while the node downloads and installs,
then lands on stopped.
If you have no node online yet, the wizard sends you to the nodes page instead of leaving you stuck.
RAM
Dylaris gives the container what you request plus 512 MB. The extra is for the JVM itself and the process around it, not for the heap. Request 4 GB and the container limit is 4.5 GB, so a 4 GB heap does not get killed the moment the JVM allocates anything outside it.
States
| State | Meaning |
|---|---|
pending_setup | Created, waiting for the node to install it |
installing | Downloading and unpacking |
stopped | Installed, not running |
online | Running |
offline | The node is unreachable, so the state is unknown |
offline is about the node, not the server. It means nobody can currently
tell you what the server is doing.
Sub-servers
One slot can hold several separate server installations, and you switch between them. Each is a full directory of its own, so a modded world and a vanilla world can live in one slot and share nothing.
Only one runs at a time. Switching stops the current one and starts the other. This is how you keep a seasonal world around without paying for a second slot.
Console and RCON
The console is live, backed by RCON, and it is a real console: what you type goes to the server and what the server prints comes back. Output streams as it happens rather than by polling.
Player management sits next to it: the online list, kick, ban, op.
Scheduled tasks
Cron-style entries per server, for restarts and console commands. A nightly
restart is two clicks; a timed say announcement is the same mechanism.
Custom tabs
You can attach your own web tools to a server's UI as an extra tab, either inline or as a popout. Useful for a map renderer, a stats page, or anything else that already has a web interface.
Tabs run through an origin-isolated proxy, so a tool you attach cannot read the panel's session out of your browser.
Profiling
Spark is built in. Start a profile from the panel, stop it, and read the result without shell access.