This repository has been archived by the owner on Jun 7, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 33
Template Backends
Marvin edited this page Mar 26, 2020
·
5 revisions
Currently there are three different backends for storing and retrieving template data in CloudNet. The following table explains them:
Name | Description |
---|---|
LOCAL |
All data is stored on the executing CloudNet-Wrapper. This is the easiest and most stable of all backends, requiring no network transfer of files when launching services. Files are strictly copied locally, so multi-wrapper setups inevidenty lead to duplication and care must be taken to reflect changes in all configured CloudNet-Wrappers for the group. |
MASTER |
All data is stored centrally on the CloudNet-Master. This removes any duplicate datastores and allows easy updates of templates in multi-wrapper setups. Due to the central datastore, starting services may need to download the current template from the CloudNet-Master, thus inducing a delay, depending on the size of the template. When changing the template, cache clearing may be necessary. |
URL |
This is a special data store, as no data can be deployed or copied into it. When launching services, a copy of the template in the .zip -format is downloaded and unpacked. The .zip -file has to contain the template as is, without any nesting in another directory inside the file. |
Incidentally these backend types are also used for Installable Plugins with small adjustments to fit the needs of downloading only the plugin without any accompanying configuration.
This means that for the URL
backend, only a .jar
-file will be downloaded.
If you have any questions feel free to join our Discord Server / CloudNETService #RELEASE 2.2.0 by CloudNetService
- Home
- Setup
- Servers and Proxys
- Server/Proxy Types
- Signs and Mobs
- Commands
- Template
- Development
- Contributing