Migrating from CloudNet
Read the old installation, take it over, leave it untouched.
MuteCloud reads a CloudNet 4 installation and takes it over without touching it.
--dry-run reports what would be taken over without changing anything. The migration reads
only; the existing installation remains intact and operational.
What is taken over
| CloudNet | MuteCloud |
|---|---|
local/tasks/*.json | groups under groups/ |
local/groups/*.json | additional templates per group |
local/templates/... | templates under layers/ |
local/services/... | working directories of persistent servers under static/ |
| SyncProxy config | MOTD, tab list and maintenance in network.toml |
| Bridge config | fallback group |
Ports are spread apart so nothing collides, the forwarding mode between proxy and servers is chosen from the oldest version in the network, and a custom server jar survives when CloudNet used one.
After the migration
- Go through
groups, check memory and limits - Stop the previous cloud before starting MuteCloud, otherwise both systems compete for the same ports
- Watch
serviceuntil everything saysläuft
Rolling back consists of stopping MuteCloud and starting CloudNet again. Nothing was removed.
Terminology
| CloudNet | MuteCloud |
|---|---|
| Task | group |
| Template | template, here in layers |
| Node | node |
| Module | built in or an addon, see addon |
cloudnet.json | mutecloud.toml |