YunoHost-Apps/vikunja_ynh
1
0
Fork 0
mirror of https://github.com/YunoHost-Apps/vikunja_ynh.git synced 2024-09-03 18:06:26 +02:00
Code Issues Activity Actions

cleaning

Browse source
This commit is contained in:
Éric Gaspar 2024-07-31 22:28:42 +02:00
parent 86278c4302
commit 840aa34cca
5 changed files with 3 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
manifest.toml
View file

@ -19,7 +19,7 @@ admindoc = "https://vikunja.io/docs/"
code = "https://kolaente.dev/vikunja/vikunja"
[integration]
yunohost = ">= 11.2.18"
yunohost = ">= 11.2.20"
helpers_version = "2.1"
architectures = "all"
multi_instance = true

2
scripts/change_url
View file

@ -34,8 +34,6 @@ domain="$new_domain"
path="$new_path"
ynh_config_add --template="config.yml" --destination="$install_dir/config.yml"
#REMOVEME? Assuming the file is setup using ynh_config_add, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chmod 600 "$install_dir/config.yml"
#=================================================
# START SYSTEMD SERVICE
#=================================================

6
scripts/install
View file

@ -46,8 +46,7 @@ executable="$(find $install_dir -name "vikunja-*" \! -name "*.sha256")"
mv "$executable" "$install_dir/vikunja"
chmod +x "$install_dir/vikunja"
#REMOVEME? Assuming the install dir is setup using ynh_setup_source, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chmod -R o-rwx "$install_dir"
#REMOVEME? Assuming the install dir is setup using ynh_setup_source, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chown -R $app:www-data "$install_dir"
#=================================================
# ADD A CONFIGURATION
#=================================================
@ -55,9 +54,6 @@ ynh_script_progression "Adding $app's configuration..."
ynh_config_add --template="config.yml" --destination="$install_dir/config.yml"
#REMOVEME? Assuming the file is setup using ynh_config_add, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chmod 400 "$install_dir/config.yml"
#REMOVEME? Assuming the file is setup using ynh_config_add, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chown "$app:$app" "$install_dir/config.yml"
#=================================================
# SYSTEM CONFIGURATION
#=================================================

2
scripts/restore
View file

@ -10,8 +10,6 @@ ynh_script_progression "Restoring $app main directory..."
ynh_restore "$install_dir"
#REMOVEME? Assuming the install dir is setup using ynh_setup_source, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chmod -R o-rwx "$install_dir"
#REMOVEME? Assuming the install dir is setup using ynh_setup_source, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chown -R "$app:www-data" "$install_dir"
#=================================================
# RESTORE THE POSTGRESQL DATABASE
#=================================================

6
scripts/upgrade
View file

@ -99,8 +99,7 @@ executable="$(find $install_dir -name "vikunja-*" \! -name "*.sha256")"
mv "$executable" "$install_dir/vikunja"
chmod +x "$install_dir/vikunja"
#REMOVEME? Assuming the install dir is setup using ynh_setup_source, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chmod -R o-rwx "$install_dir"
#REMOVEME? Assuming the install dir is setup using ynh_setup_source, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chown -R $app:www-data "$install_dir"
#=================================================
# UPDATE A CONFIG FILE
#=================================================
@ -108,9 +107,6 @@ ynh_script_progression "Updating $app's configuration files..."
ynh_config_add --template="config.yml" --destination="$install_dir/config.yml"
#REMOVEME? Assuming the file is setup using ynh_config_add, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chmod 400 "$install_dir/config.yml"
#REMOVEME? Assuming the file is setup using ynh_config_add, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chown $app:$app "$install_dir/config.yml"
#=================================================
# REAPPLY SYSTEM CONFIGURATIONS
#=================================================