Templates and drafts
A template holds the files and the runtime its servers start from. For Minecraft the runtime is the server jar, its version and the Java image. Every group runs one template.
Templates build on each other
A template can have one parent, like lobby/default on global/paper. The child takes its parent's runtime and files and can override any of them. When two templates ship the same file, the nearest one wins.
Creating your first group makes a global template and the group's own template on top of it.
The template always wins
A file a template ships replaces the server's own copy every time the server starts. Files no template ships, like worlds and player data, stay where they are.
So change config in the template, not on the server. A change made on the server is gone after its next restart.
Versions
Publishing a template makes a version. A version is read-only and pins one exact build of its jar, so every server on it runs the same files.
Each server remembers the version of every template it runs. When a newer version is live, the server counts as outdated, and the group says how many are.
Drafts
To change a template, start a draft from it. A draft lives on a node you pick, and you can open several at once, each with its own name.
Edit the files in the panel's file manager, or over SFTP. The panel gives each person a login per draft that shows the draft merged with its parents. Writes land in the draft only.
The server software and Java version also change in a draft, under the draft's Settings. Atlas fetches the new jar into the draft in the background, and the draft can't be published until the fetch finishes. A live template shows its software read-only, with a button to change it in a draft.
Publish a draft
Choose Publish on the draft. Atlas asks what to do with outdated servers:
- Now restarts one first, then the rest a few at a time.
- Later leaves them for their next restart.
The first draft to publish wins. Any other draft of the same template is then behind, and updates to the new version before it can publish. Where both changed a file, you keep your copy or take the version's.
Roll back
Under Versions, choose Make live on any earlier version. Servers on the newer version count as outdated and follow it on their next restart, or right away if you restart them.
Take files from a server
A running server can hand its files to a draft. Use Import from server in the draft, or Copy to template in the server's Files tab. Atlas only takes files that differ from the draft, and each change names the server it came from.