2021-03-19 19:47:11 +01:00
|
|
|
#!/bin/bash
|
|
|
|
|
|
|
|
#=================================================
|
|
|
|
# GENERIC START
|
|
|
|
#=================================================
|
|
|
|
# IMPORT GENERIC HELPERS
|
|
|
|
#=================================================
|
|
|
|
|
|
|
|
source _common.sh
|
|
|
|
source /usr/share/yunohost/helpers
|
|
|
|
|
|
|
|
#=================================================
|
|
|
|
# MANAGE SCRIPT FAILURE
|
|
|
|
#=================================================
|
|
|
|
|
|
|
|
# Exit if an error occurs during the execution of the script
|
|
|
|
ynh_abort_if_errors
|
|
|
|
|
|
|
|
#=================================================
|
|
|
|
# RETRIEVE ARGUMENTS FROM THE MANIFEST
|
|
|
|
#=================================================
|
|
|
|
|
|
|
|
domain=$YNH_APP_ARG_DOMAIN
|
2021-03-29 18:57:36 +02:00
|
|
|
path_url=`echo "/" `ynh_app_setting_get --app=$YNH_APP_ARG_APP_ID --key=path` "/icecoder"`
|
2021-03-19 19:47:11 +01:00
|
|
|
|
|
|
|
### If it's a multi-instance app, meaning it can be installed several times independently
|
|
|
|
### The id of the app as stated in the manifest is available as $YNH_APP_ID
|
|
|
|
### The instance number is available as $YNH_APP_INSTANCE_NUMBER (equals "1", "2"...)
|
|
|
|
### The app instance name is available as $YNH_APP_INSTANCE_NAME
|
|
|
|
### - the first time the app is installed, YNH_APP_INSTANCE_NAME = ynhexample
|
|
|
|
### - the second time the app is installed, YNH_APP_INSTANCE_NAME = ynhexample__2
|
|
|
|
### - ynhexample__{N} for the subsequent installations, with N=3,4...
|
|
|
|
### The app instance name is probably what interests you most, since this is
|
|
|
|
### guaranteed to be unique. This is a good unique identifier to define installation path,
|
|
|
|
### db names...
|
2021-03-20 07:08:56 +01:00
|
|
|
app=$YNH_APP_INSTANCE_NAME
|
2021-03-19 19:47:11 +01:00
|
|
|
|
|
|
|
#=================================================
|
|
|
|
# CHECK IF THE APP CAN BE INSTALLED WITH THESE ARGS
|
|
|
|
#=================================================
|
|
|
|
### About --weight and --time
|
|
|
|
### ynh_script_progression will show to your final users the progression of each scripts.
|
|
|
|
### In order to do that, --weight will represent the relative time of execution compared to the other steps in the script.
|
|
|
|
### --time is a packager option, it will show you the execution time since the previous call.
|
|
|
|
### This option should be removed before releasing your app.
|
|
|
|
### Use the execution time, given by --time, to estimate the weight of a step.
|
|
|
|
### A common way to do it is to set a weight equal to the execution time in second +1.
|
|
|
|
### The execution time is given for the duration since the previous call. So the weight should be applied to this previous call.
|
2021-03-20 13:10:15 +01:00
|
|
|
ynh_script_progression --message="Validating installation parameters..." --weight=1
|
2021-03-19 19:47:11 +01:00
|
|
|
|
|
|
|
### If the app uses NGINX as web server (written in HTML/PHP in most cases), the final path should be "/var/www/$app".
|
|
|
|
### If the app provides an internal web server (or uses another application server such as uWSGI), the final path should be "/opt/yunohost/$app"
|
2021-03-29 18:57:36 +02:00
|
|
|
final_path=/var/www/$YNH_APP_ARG_APP_ID/icecoder
|
2021-03-19 19:47:11 +01:00
|
|
|
test ! -e "$final_path" || ynh_die --message="This path already contains a folder"
|
|
|
|
|
2021-03-21 15:12:29 +01:00
|
|
|
# Register (book) web path
|
2021-03-28 19:29:29 +02:00
|
|
|
ynh_webpath_register --app=$app --domain=$domain --path_url=$path_url
|
|
|
|
|
2021-03-19 19:47:11 +01:00
|
|
|
#=================================================
|
|
|
|
# STORE SETTINGS FROM MANIFEST
|
|
|
|
#=================================================
|
2021-03-20 13:10:15 +01:00
|
|
|
ynh_script_progression --message="Storing installation settings..." --weight=1
|
2021-03-19 19:47:11 +01:00
|
|
|
|
|
|
|
ynh_app_setting_set --app=$app --key=domain --value=$domain
|
|
|
|
ynh_app_setting_set --app=$app --key=path --value=$path_url
|
|
|
|
|
|
|
|
#=================================================
|
|
|
|
# DOWNLOAD, CHECK AND UNPACK SOURCE
|
|
|
|
#=================================================
|
2021-03-20 13:10:15 +01:00
|
|
|
ynh_script_progression --message="Setting up source files..." --weight=1
|
2021-03-19 19:47:11 +01:00
|
|
|
|
|
|
|
### `ynh_setup_source` is used to install an app from a zip or tar.gz file,
|
|
|
|
### downloaded from an upstream source, like a git repository.
|
|
|
|
### `ynh_setup_source` use the file conf/app.src
|
|
|
|
|
|
|
|
ynh_app_setting_set --app=$app --key=final_path --value=$final_path
|
|
|
|
# Download, check integrity, uncompress and patch the source from app.src
|
2021-03-29 18:57:36 +02:00
|
|
|
ynh_setup_source --dest_dir="$final_path"
|
|
|
|
|
|
|
|
#=================================================
|
|
|
|
# SPECIFIC SETUP
|
|
|
|
#=================================================
|
|
|
|
|
|
|
|
# Change config (ban editor's folder)
|
|
|
|
php -f "../conf/config.php"
|
|
|
|
|
|
|
|
#=================================================
|
2021-03-19 19:47:11 +01:00
|
|
|
|
|
|
|
#=================================================
|
|
|
|
# GENERIC FINALIZATION
|
|
|
|
#=================================================
|
|
|
|
# SECURE FILES AND DIRECTORIES
|
|
|
|
#=================================================
|
|
|
|
|
|
|
|
### For security reason, any app should set the permissions to root: before anything else.
|
|
|
|
### Then, if write authorization is needed, any access should be given only to directories
|
|
|
|
### that really need such authorization.
|
|
|
|
|
2021-03-29 18:57:36 +02:00
|
|
|
# Set permissions to app files
|
|
|
|
chown -R $YNH_APP_ARG_APP_ID $final_path
|
|
|
|
|
2021-03-19 19:47:11 +01:00
|
|
|
#=================================================
|
|
|
|
# SETUP LOGROTATE
|
|
|
|
#=================================================
|
2021-03-20 13:10:15 +01:00
|
|
|
ynh_script_progression --message="Configuring log rotation..." --weight=1
|
2021-03-19 19:47:11 +01:00
|
|
|
|
|
|
|
### `ynh_use_logrotate` is used to configure a logrotate configuration for the logs of this app.
|
|
|
|
### Use this helper only if there is effectively a log file for this app.
|
|
|
|
### If you're not using this helper:
|
|
|
|
### - Remove the section "BACKUP LOGROTATE" in the backup script
|
|
|
|
### - Remove also the section "REMOVE LOGROTATE CONFIGURATION" in the remove script
|
|
|
|
### - As well as the section "RESTORE THE LOGROTATE CONFIGURATION" in the restore script
|
|
|
|
### - And the section "SETUP LOGROTATE" in the upgrade script
|
|
|
|
|
|
|
|
# Use logrotate to manage application logfile(s)
|
|
|
|
ynh_use_logrotate
|
|
|
|
|
|
|
|
#=================================================
|
2021-03-29 18:57:36 +02:00
|
|
|
# INTEGRATE SERVICE IN YUNOHOST
|
|
|
|
#=================================================
|
|
|
|
ynh_script_progression --message="Integrating service in YunoHost..." --weight=1
|
|
|
|
|
|
|
|
### `yunohost service add` integrates a service in YunoHost. It then gets
|
|
|
|
### displayed in the admin interface and through the others `yunohost service` commands.
|
|
|
|
### (N.B.: this line only makes sense if the app adds a service to the system!)
|
|
|
|
### If you're not using these lines:
|
|
|
|
### - You can remove these files in conf/.
|
|
|
|
### - Remove the section "REMOVE SERVICE INTEGRATION IN YUNOHOST" in the remove script
|
|
|
|
### - As well as the section "INTEGRATE SERVICE IN YUNOHOST" in the restore script
|
|
|
|
### - And the section "INTEGRATE SERVICE IN YUNOHOST" in the upgrade script
|
|
|
|
|
|
|
|
yunohost service add $app --description="ICEcoder logs" --log="/var/log/$app/$app.log"
|
|
|
|
|
|
|
|
### Additional options starting with 3.8:
|
|
|
|
###
|
|
|
|
### --needs_exposed_ports "$port" a list of ports that needs to be publicly exposed
|
|
|
|
### which will then be checked by YunoHost's diagnosis system
|
|
|
|
### (N.B. DO NOT USE THIS is the port is only internal!!!)
|
|
|
|
###
|
|
|
|
### --test_status "some command" a custom command to check the status of the service
|
|
|
|
### (only relevant if 'systemctl status' doesn't do a good job)
|
|
|
|
###
|
|
|
|
### --test_conf "some command" some command similar to "nginx -t" that validates the conf of the service
|
|
|
|
###
|
|
|
|
### Re-calling 'yunohost service add' during the upgrade script is the right way
|
|
|
|
### to proceed if you later realize that you need to enable some flags that
|
|
|
|
### weren't enabled on old installs (be careful it'll override the existing
|
|
|
|
### service though so you should re-provide all relevant flags when doing so)
|
2021-03-19 19:47:11 +01:00
|
|
|
|
2021-03-20 08:20:38 +01:00
|
|
|
|
2021-03-19 19:47:11 +01:00
|
|
|
#=================================================
|
|
|
|
# END OF SCRIPT
|
|
|
|
#=================================================
|
|
|
|
|
2021-03-20 13:10:15 +01:00
|
|
|
ynh_script_progression --message="Installation of $app completed" --last
|