Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to multicraft 2.0 template function #12

Open
larsomen opened this issue Jun 1, 2015 · 0 comments
Open

Update to multicraft 2.0 template function #12

larsomen opened this issue Jun 1, 2015 · 0 comments

Comments

@larsomen
Copy link

larsomen commented Jun 1, 2015

I just found out that Multicraft 2.0 will have a template function that basicly does the same as this.
I think i will look into it today, if it works like expected i'll convert these scripts to multicraft 2.0 templates.

readme.txt in the template folder:

The directory structure of a template is:

templates/
/templatename/ - Root template directory
/files/ - Files to be copied (optional)
template.conf - Template configuration (optional)
initialize.sh - Initialize script (optional)
beforeDelete.sh - Before delete script (optional)
afterDelete.sh - After delete script (optional)
beforeSetup.sh - Before setup script (optional)
afterSetup.sh - After setup script (optional)

OR:

templates/
templatename.zip - Same contents as /templatename/ above.

Root template directory

The directory name "templatename" is a unique name for this template. All files
for this template are put in this directory.

The "files" directory

The files in this directory will be copied to the server base directory during
the setup. This directory is optional.

Template configuration file

The "template.conf" file contains the template configuration, this file is
optional. If it does not exist all configuration options will use the
default values and the template name will be the same as the directory name.
See the template.conf of the provided default template for the full
documentation of available settings.

Template script files

If these files exist and no alternative command is configured in the
template.conf file they will be run at the appropriate time during the setup
process. All of these files are optional.
The setup steps at which scripts can be run are:
initialize
Before anything else is done this script will be run
beforeDelete
If the user wants to have all server files deleted (or if this is enforced
in the template.conf) this will be run before deleting the server files.
Here you can save certain information to a temporary location for example.
afterDelete
Analogous to "beforeDelete" this will be run right after the server files
have been deleted. The beforeDelete/afterDelete scripts are not run if the
server files are not deleted.
beforeSetup
This is run right before the files from the "files" directory are copied to
the server base directory.
afterSetup
This is run right after the files have been copied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant