Cron jobs play a vital part in the day to day functions and operations to your script. If you neglect to setup the cron jobs, you may start seeing items build up and will take a task to get items caught up.
To setup your cron jobs, login to your cPanel and click on the cron jobs icon – we recommend using the ‘advanced’ cron job setup area.
Once inside, you will need to setup the following cron jobs to manage the day to day items of your AutoPilot.
Ran Every 8 Hours
0 */8 * * * GET http://yoursite.com/admin/cron_resolver.php > /dev/null
o This one runs the resolver every 8 hours to check on domain resolve status.
Ran Daily at 12:15 AM
15 0 * * * GET http://yoursite.com/admin/cron_1215.php > /dev/null
o This cron job will backup your database nightly
o This will build your invoices, cron jobs and remind your clients of billings
o This will update your affiliate logs
ATTENTION THOSE WHO MAY BE SECURED DIFFERENTLY
Some may run into problems with this cron job not running due to https:// being in place. We have writing in a replacement command that will replace https:// with http:// due to errors that were encountered. One, though, does cause the need to have 3 separate cron jobs created in place of this one due to different circumstances.
If your site is secured similar to this: https://secure.mysite.com/admin/index.php – then you will need to setup singular cron jobs for each of the three that run in the 1215 cron.
5 0 * * * GET http://mysite.com/admin/cron_dbbackup.php > /dev/null
10 0 * * * GET http://mysite.com/admin/cron_invoice.php > /dev/null
15 0 * * * GET http://mysite.com/admin/cron_affiliate.php > /dev/null
Be sure to remove the cron_1215.php cron job if you are running them singularly.
Ran on Fridays
5 0 * * 6 GET http://yoursite.com/admin/cron_weekly_sales.php > /dev/null
o This will generate a report on weekly sales since the previous Saturday
Ran the last day of the month
0 0 30 * * GET http://yourdomain.com/admin/cron_reports_new_monthly_signups.php > /dev/null
0 0 30 * * GET http://yourdomain.com/admin/cron_reports_monthly_revenue.php> /dev/null
We chose the 30th for these to capture as many months as possible. There will be one month that fluctuates and does not meet the 30 day cycle minimum per month. You do have an option here. You can create a cron job to run on the last day of each month or, use the two stock ones as