public/dropshell
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 44 Wiki Activity

Tidying

Browse Source
This commit is contained in:
Your Name 2025-05-03 20:30:06 +12:00
parent 9b9a536697
commit c6b7e2bb41
1 changed files with 12 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
templates/example-nginx/README.txt
View File

@ -10,12 +10,13 @@ When they are run, the following environment variables will be set:
- everything in _default.env
- everything in the server's particular service.env file (defaults in example/service.env)
The optional backup and restore scripts get a second argument, which is the backup file to create/restore
(must be a single tgz file).
The optional backup and restore scripts get two additional arguments, which are the backup file to create/restore
(must be a single tgz file), and an empty temporary directory on the server which automatically gets cleaned up.
Mandatory scripts are:
- install.sh
- uninstall.sh
- install.sh (installs, or if already installed updates - non-destructive)
- uninstall.sh (preserves data)
- nuke.sh (deletes all data)
Optional standard scripts are:
- start.sh
@ -30,4 +31,10 @@ Optional standard scripts are:
The example/ folder gets copied to the service's configuration, edited for the particular server settings,
then copied onto the server. The location is server-specific, but can be accessed via CONFIG_PATH.
You can use it to store things like an nginx config file (this example does not).
You can use it to store things like an nginx config file (this simple example does not).
The example/.template_info.env must contain the TEMPLATE= definition, which must match the template folder name
(in this case 'example-nginx').
You can start a new template with the command:
dropshell create-template <TEMPLATE_NAME>