Skip to content

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

Closed

Description

@bugy
No description provided.

Activity

  1. mitchtchesnitch commented on Nov 3, 2020

    @mitchtchesnitch

    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:

    image

    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}`

  2. bugy commented on Nov 3, 2020

    @bugy
    OwnerAuthor

    Hehe, nice! :)

    One side note question out of curiosity: why are you using "file_recursive": "True"? It's not necessary, when you don't have nested folders

  3. mitchtchesnitch commented on Nov 3, 2020

    @mitchtchesnitch

    You're right, now that I think of it, that doesn't make sense, I removed that:D

  4. Gamma-Software commented on Aug 3, 2021

    @Gamma-Software

    I replaced ${COMMAND} ${FILE} by ${COMMAND} "${FILE}"
    Reason: I was not able to remove schedules configs with space in names

  5. added this to the 1.18.0 milestone on Sep 3, 2021
  6. added a commit that references this issue on Feb 17, 2023
  7. bugy commented on Feb 17, 2023

    @bugy
    OwnerAuthor

    just a note: this issue is about adding a possibility on admin UI to enable scheduling for a particular script configuration:
    image

    And this is resolved now

    There is a separate ticket in #625 for managing created schedules

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions