Thought I'd leave my workaround here as well, since I've seen it mentioned in some threads, but no actual examples.

Simple script that checks the folder where the schedules are stored, giving you the option to "manage them", as in delete or list contents. Not pretty but does the job:

Runner:

{ "name": "\ud83d\udcbbAdmin Schedule Management", "script_path": "/Script-Server/conf/scripts/Scheduled/admin_schedule_management.sh", "working_directory": "/", "description": "Script used for administering schedules", "group": "Administration", "requires_terminal": true, "allowed_users": [ "@blabla"], "parameters": [ { "name": "Action", "required": true, "type": "list", "description": "Which action would you like to perform?", "default": "list", "values": [ "list", "delete" ] }, { "name": "File", "required": true, "type": "server_file", "description": "Which file do you want to work on?", "file_dir": "/Script-Server/conf/schedules", "file_type": "file" } ] }

Script:

`#!/bin/sh

ACTION=${1}
FILE_RAW=${2}
FILE=$(echo $FILE_RAW | sed 's/ /\ /g') #Strips spaces from filenames, posix doesn't like that.

case ${ACTION} in
list)
COMMAND="cat"
;;
delete)
COMMAND="rm"
;;
*)
printf "$red" "Invalid option, please chose list/delete"
esac

printf "Okay, running ${COMMAND} on the selected file: ${FILE}"
printf "\n\n"
${COMMAND} ${FILE}`

Uh oh!

Admin script configuration UI: add possibility to enable/disable scheduling #362

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions