Service
The service is the central component of CloudNet. A CloudNet service is the designation for a Minecraft server created and managed by CloudNet. This means that every single Minecraft server corresponds to exactly one service. CloudNet's services are created and scaled based on previously set settings. All these settings can be configured in the associated Task.
Lifecycle
The lifecycles of a service represent the current status of the service. At the same time, changing from one lifecycle to another brings about the consequences described here.
Prepared
The Prepared lifecycle is the first cycle in which a newly created service is placed. This cycle represents that the service has been created within CloudNet. As soon as the service is in this cycle, every Node in the CLUSTER knows the service and it can be controlled via the API and commands.
Running
The Running lifecycle is usually the second cycle of a service. The lifecycle means
that all files from the configured Templates have been copied
and then the service has been started. This means specifically that CloudNet has established a connection to the service
and the actual Minecraft server (such as the Spigot server) has been started. Based on the settings in the
task, the service can now be found in local/services or in temp/services.
The Running lifecycle is set as soon as the installed server software has been started. This does not mean that this service is immediately accessible, as the software usually needs a few seconds to start.
Stopped
The Stopped lifecycle is set when the stop of the service is requested. The process of the service, i.e. the software such as Paper, is terminated. Then the files to be deleted are deleted. Based on the settings in the Task, there are now two scenarios:
- If the autoDeleteOnStop option is enabled in the task, the service is set to the DELETED state.
- Otherwise, the service is marked as PREPARED again. In this state, the temporary files
are still visible in
temp/service.
Deleted
The Deleted lifecycle is set when the service has been permanently removed from the cloud. At this point, the entire post-processing process has been completed. If staticServices are disabled in the task, the temporary files are permanently removed at this point.