STYGION Panel a0.3.2

The console belongs to the server now, not to whoever happens to be looking at it. Two complaints, one cause.

Pressing Start shows the start

A container's log outlives its restarts, so the console used to open on the previous run: a wall of text from a server that had already stopped, a pause, and only then the one that was actually booting. An hour-old crash read as if it had just happened.

The console is now emptied when a server starts, and says what is being launched before the container has printed anything of its own:

[stygion] Starting Survival
[stygion] Image: ghcr.io/pelican-eggs/yolks:java_21
[stygion] Command: java -Xms4G -Xmx8G -jar server.jar nogui
[stygion] Port: 25565/tcp
[stygion] ──────────────────────────────────────────

A server pulling a big modpack can sit silent for a minute, and a console that shows nothing in that minute looks broken. This is also the quickest way to see that a startup command is wrong.

It is connected the whole time

The stream used to start when you opened the page and die when you closed it. Press Start, switch tabs, come back — the first seconds of the boot had happened with nobody streaming, and were gone.

A running server now has one reader that lives as long as it does, feeding a buffer the panel keeps. Opening the console is instant because the lines are already there, nothing is missed because nobody was watching, and ten people watching one server costs exactly what one does.

The same buffer carries the egg install, so watching a server being installed and watching it run are one screen rather than two that hand over at an invisible moment. A panel restart — which is what an update is — no longer takes every console with it: servers that are already running are picked back up.

A command you type is echoed to everyone watching, not just to you.

Also

Consoles reconnect on their own and no longer wait for a server to be running before connecting at all, which is what made the first seconds of a boot arrive late or not at all.