In order to update, craft build must be run then the server must be destroyed and rebuilt. Previously this was just stopping and starting the server as there was no persistence except backups.
Servers are now persistent by default (containers use volumes) and are stopped/started instead of killed/recreated. Now, to update a default server the user would need to docker rm it which defeats the purpose of using something like craft.
We need a command to reset (destroy and recreate) a server. The process to update servers should be:
craft build
craft reset server1 server2 server3
Adding an update command which rebuilds the container and resets the server is tempting. However that's a lot of high level actions being taken automatically.
Bedrock seems to force all updates so there probably isn't a need to add support for multiple concurrent versions.
In order to update,
craft buildmust be run then the server must be destroyed and rebuilt. Previously this was just stopping and starting the server as there was no persistence except backups.Servers are now persistent by default (containers use volumes) and are stopped/started instead of killed/recreated. Now, to update a default server the user would need to
docker rmit which defeats the purpose of using something likecraft.We need a command to reset (destroy and recreate) a server. The process to update servers should be:
Adding an
updatecommand which rebuilds the container and resets the server is tempting. However that's a lot of high level actions being taken automatically.Bedrock seems to force all updates so there probably isn't a need to add support for multiple concurrent versions.