Cron Jobs: Difference between revisions
Created page with "== Cron Jobs == In Plesk, cron jobs are called `Scheduled Tasks`. == Cron Jobs Affect Account Load == Scheduled Tasks count towards your total account load. This means that running too many cron jobs or starting a cron job to run every 1 minute risks your account getting suspended for high server usage. Refer to the Cron Jobs section of our Suspension Policy for more details. == Setting up a Scheduled Task == To access the cron job section, n..." |
No edit summary |
||
Line 1: | Line 1: | ||
= Cron Jobs = | |||
In Plesk, cron jobs are called `Scheduled Tasks`. | In Plesk, cron jobs are called `Scheduled Tasks`. | ||
= Cron Jobs Affect Account Load = | |||
Scheduled Tasks count towards your total account load. This means that running too many cron jobs or starting a cron job to run every 1 minute risks your account getting suspended for high server usage. Refer to the Cron Jobs section of our [[:Suspension_Policy|Suspension Policy]] for more details. | Scheduled Tasks count towards your total account load. This means that running too many cron jobs or starting a cron job to run every 1 minute risks your account getting suspended for high server usage. Refer to the Cron Jobs section of our [[:Suspension_Policy|Suspension Policy]] for more details. | ||
= Setting up a Scheduled Task = | |||
To access the cron job section, navigate to: | To access the cron job section, navigate to: | ||
Line 13: | Line 13: | ||
'''Login > Plesk > Websites & Domains > [ domain ] > Scheduled Tasks > `Add Task`''' | '''Login > Plesk > Websites & Domains > [ domain ] > Scheduled Tasks > `Add Task`''' | ||
[[File:plesk-scheduled-tasks.png]] | |||
= Cron Jobs are chrooted = | |||
Scheduled Tasks run in a chroot environment with limited access to binaries and executables for security reasons. | Scheduled Tasks run in a chroot environment with limited access to binaries and executables for security reasons. | ||
This means you cannot directly access certain programs or scripts outside of your home directory. | This means you cannot directly access certain programs or scripts outside of your home directory. | ||
= Working Around the chroot = | |||
Some options to work around the chroot environment when setting up a Scheduled Task include: | Some options to work around the chroot environment when setting up a Scheduled Task include: | ||
= Flask Endpoint = | |||
Set up a Flask application and create an endpoint like `domain.helioho.st/update`, then use the "Fetch a URL" option inside Scheduled Tasks to access it via `https`. | Set up a Flask application and create an endpoint like `domain.helioho.st/update`, then use the "Fetch a URL" option inside Scheduled Tasks to access it via `https`. | ||
If you're new to Flask or want a more detailed guide, check out this [Flask tutorial] | If you're new to Flask or want a more detailed guide, check out this [[:Flask|Flask tutorial]] to help you get started. | ||
= Python = | |||
Set up a Python script in the `cgi-bin` directory, then use the "Fetch a URL" option inside Scheduled Tasks to access the file via `https`. | Set up a Python script in the `cgi-bin` directory, then use the "Fetch a URL" option inside Scheduled Tasks to access the file via `https`. | ||
If you're new to Python or want a more detailed guide, check out this [[: | If you're new to Python or want a more detailed guide, check out this [[:Python|Python tutorial]] to help you get started. | ||
[[File:plesk-schedule-a-task.png]] |
Revision as of 16:10, 4 October 2024
Cron Jobs
In Plesk, cron jobs are called `Scheduled Tasks`.
Cron Jobs Affect Account Load
Scheduled Tasks count towards your total account load. This means that running too many cron jobs or starting a cron job to run every 1 minute risks your account getting suspended for high server usage. Refer to the Cron Jobs section of our Suspension Policy for more details.
Setting up a Scheduled Task
To access the cron job section, navigate to:
Login > Plesk > Websites & Domains > [ domain ] > Scheduled Tasks > `Add Task`
Cron Jobs are chrooted
Scheduled Tasks run in a chroot environment with limited access to binaries and executables for security reasons. This means you cannot directly access certain programs or scripts outside of your home directory.
Working Around the chroot
Some options to work around the chroot environment when setting up a Scheduled Task include:
Flask Endpoint
Set up a Flask application and create an endpoint like `domain.helioho.st/update`, then use the "Fetch a URL" option inside Scheduled Tasks to access it via `https`.
If you're new to Flask or want a more detailed guide, check out this Flask tutorial to help you get started.
Python
Set up a Python script in the `cgi-bin` directory, then use the "Fetch a URL" option inside Scheduled Tasks to access the file via `https`.
If you're new to Python or want a more detailed guide, check out this Python tutorial to help you get started.