Skip to content

Anonymous

My feedback

4 results found

  1. 19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anonymous supported this idea  · 
  2. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    cronjobs can easily be managed by Linux commands already. They may not be sourced from Plesk, but all tools already exist on the operating system. As cronjobs are read by Plesk from disk, manipulating the corresponding files on disk will set everything you wish. Individual cron files are stored in /var/spool/cron and can be text-edited. You can add files, edit files, append files and delete files using Linux commands. You can also stream-edit files (e.g. insert a commend tag before a line with sed) and also create Linux control while-loops to apply changes to filtered files. Cron can also be controlled directly (https://man7.org/linux/man-pages/man1/crontab.1.html). 

    Please let us know in details what you are missing or please provide an example how you would like Plesk to work with cron instead.

    -- PD

    An error occurred while saving the comment
    Anonymous commented  · 

    It's true that you can manage cronjobs by using crontab or by editting the files under /var/spool/cron.
    But doing that can be a real pain, especially for users that are not that familar with Linux/Plesk.

    You can use sed to edit the cron files, but dependig on what you want to do you have to use cryptic regular expressions for changing execution times etc.

    You also have to look up the corresponding system user first in order to know which file to edit.
    When managing Plesk cronjobs you usually want to do that based on the domain name of the hosting, not based on the system user.

    And most important, in Plesk you can do more than than just managing simple cronjobs.
    You can also create cronjobs that run PHP scripts or call URLs. It's not possible to do the same using the Linux command line tools, at least not without deeper knowledge how Plesk treats those "special" cronjobs internally or using an existing Plesk cronjob as a template.

    So a Plesk CLI utity for setting up cronjobs the same way as in Plesk, without needing to know the cron time format, the location of the PHP executables, how to call URLs via CLI etc. would be very welcome.

    Here some examples how adding cronjobs with that utily could look like:

    plesk bin cron --add -domain domain.tld -type command -command /usr/bin/example -execute hourly -minute 12
    plesk bin cron --add -domain domain.tld -type php -php-version 8.1 -command /path/to/php/script.php -args "someargs" -execute weekly -day sun -hour 1 -minute 23 --description "Some description"
    plesk bin cron --add -domain domain.tld -type url -command https://example.com/ -execute daily -hour 12 -minute 34

    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    Managing cronjobs via CLI is one of the big missing features in current Plesk versions since almost anything else can be done via command line already. Plesk should definitely add this feature in future releases.

  4. 88 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    Would be great to have it implemented!

Feedback and Knowledge Base