Skip to main content

Cron Jobs in the Staging Environment

In the staging environment you can safely develop your site without disturbing the production site. When the staging is created, it is an exact copy of your current production environment, including e.g. any cron jobs you might have. Triggering cron jobs simultaneously from production and staging sites may in some cases cause them to fail, resulting in them disturbing your production site's functionality.

Editing the crontab

You can check what cron jobs you have in staging and remove any jobs that you don't absolutely need by opening the crontab in text editor with the following command:

crontab -e

If some cron jobs are necessary in the staging and the scripts access your own site, note that example.com refers to the production site. If you want to access the staging site, you need to add the seravo_shadow attribute to the URL, e.g. example.com?seravo_shadow=456def.

Did this answer your question?