Guides
Cron and scheduling, explained properly.
Long-form references for specific stacks and hosting setups. Pick by your language or database, jump straight to the runtime guide for cPanel or Docker, or hit the troubleshooting hub when something is broken right now.
Shorter tutorials and integration posts live on the blog. Copy-paste cron expressions are at /recipes.
Languages & frameworks
Python cron jobs (all four ways)
crontab, in-process schedulers, AWS/GCP platform cron, and external HTTP cron hitting Flask or FastAPI. Side-by-side with code.
Django cron jobs (all four ways)
crontab + manage.py, django-q / django-celery-beat / APScheduler, platform cron, and external HTTP cron hitting a Django view. Side-by-side with code.
Laravel cron jobs (all four ways)
Laravel Scheduler with `schedule:run`, supervised workers, platform cron (Forge, Vapor, Heroku), and external HTTP cron hitting Artisan. Side-by-side with code.
PHP cron jobs (all four ways)
crontab + php-cli, long-running daemons (Workerman / ReactPHP), framework schedulers, and external HTTP cron hitting a PHP-FPM endpoint. Plus the cli-vs-fpm pitfalls.
Node.js cron jobs (all four ways)
crontab + node, node-cron / BullMQ / Agenda in-process, platform cron (Vercel, Workers, Lambda), and external HTTP cron. Plus the duplicate-fire trap when you cluster.
Databases
Postgres cron jobs (all four ways)
pg_cron (when your host allows it), long-running connection runners, platform schedulers, and external HTTP cron hitting a /cron/run endpoint. Plus advisory locks for safe overlap.
Supabase cron jobs (all three ways)
pg_cron inside Postgres, Supabase Cron (the UI), and external HTTP cron hitting an Edge Function. When to pick which, with code.
Hosts & containers
cPanel cron jobs
Where to click in cPanel, the minimum command line, common PATH and PHP gotchas, and when to move scheduling to external HTTP cron.
Docker cron jobs (four patterns)
Why cron-in-container breaks in prod, when a sidecar or CronJob fits, and why external HTTP cron keeps images single-purpose.
Troubleshooting
Not on this list?
Crontap fires any HTTPS URL on a cron.
The guides above cover the stacks we see most often. The product is target-agnostic. If your language ships an HTTP server and your host exposes a URL, Crontap can drive it on any cadence in any IANA timezone.
Ready to fix it?
Point Crontap at any URL. Pick any cron. Done.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
Free forever tier ・ No credit card required
/wp-cron.php?doing_wp_cron=1
Schedule
"every 5 minutes"
Next
in 23s