Wizard's Toolkit has files prepared for common cron job operations. By default the cron jobs are located in a /cron folder which is public on the webserver. You can (and probably should) move that to a non-public location on the server. Since Nginx, Apache and other webservers have different methodologies for calling CRON jobs, those details can be decided by your DevOps person.

All cron job files are kept in the /cron/ folder. Of course, you can move these to a different folder as needed.

WTK has a default robots.txt which tells search engines to ignore the /cron/ folder and other folders which generally should not be crawled, for example the /exports/ folder. This robots.txt should be uploaded to your root directory of your web server. Modify it as needed for your specific needs.

To prevent calls from outside sources to your CRON jobs, a `pw` parameter is required. The password is specific to your server and you set what you want the password to be in the /wtk/wtkServerInfo.php file.

$gloAuthStatus = 'setYourUniqueCodeHere';  // guarantees uniqueness for login security level checks

Whatever value you set there, prepend 'wtk' before it when calling your cron jobs. For example, to trigger the monthly.php cron job you would call it this way:

https://your-domain.com/cron/monthly.php?pw=wtksetYourUniqueCodeHere

Different OS have different calling methods so check with your DevOps and verify the settings used work as expected and meet your security requirements. This is just one possible way of defining a cron job to call a specific web page:

/usr/bin/curl --silent --insecure --output - https://your-domain.com/cron/minute.php?pw=wtksetYourUniqueCodeHere > /dev/null 2>&1

These pages provide a solid starting point for any client. Each client's needs are going to be very specific, but using these as a starting point gives you a solid framework.

Test

These can easily be managed in the data table aptly named `wtkBackgroundActions`.