Deploy Cronicle
Cron replacement with a web UI: schedule, run and log jobs and scripts
Just deployed
/opt/cronicle/data
Deploy and Host Cronicle on Railway
Cronicle is an open-source task scheduler and runner with a web UI, written in Node.js. It's a friendlier replacement for cron: you schedule shell scripts, HTTP requests or your own plugins, run them on demand, watch live logs, and keep a searchable history of every job with CPU and memory stats.
About Hosting Cronicle
Hosting Cronicle means running its Node.js server, keeping its storage on persistent disk, and making sure the same server stays primary across restarts. This template builds the official Cronicle 0.9.146 release on a pinned Node.js 24 image from a public GitHub repo. It keeps all storage (events, users, API keys, job history and logs) on a Railway volume, pins the server hostname so the scheduler resumes after every redeploy, and replaces Cronicle's well-known admin/admin login with a generated password. The web UI gets a Railway domain with HTTPS, and Railway checks its health at /api/app/ping.
Common Use Cases
- Run scheduled shell scripts, backups and clean-up jobs with logs and alerts in one place
- Call webhooks or APIs on a schedule with the built-in HTTP Request plugin
- Trigger jobs on demand from other apps through Cronicle's REST API and API keys
Dependencies for Cronicle Hosting
- A Railway volume for Cronicle's file storage (included)
- Optional: an SMTP server for e-mail notifications
Deployment Dependencies
- Cronicle source and releases: https://github.com/jhuckaby/Cronicle/releases
- Cronicle documentation: https://github.com/jhuckaby/Cronicle#readme
- Template repo: https://github.com/aalfath/cronicle-railway-template
Implementation Details
Log in as admin with the ADMIN_PASSWORD value from the service's Variables tab. Allow up to a minute after a deploy for the server to become primary before you create events. The password is applied only on the first boot, so change it later in the UI under My Account.
Any Cronicle setting can be set with a variable named CRONICLE_ plus the setting name, using __ for nested keys (for example CRONICLE_WebServer__http_timeout). For e-mail, add CRONICLE_smtp_hostname, CRONICLE_smtp_port and CRONICLE_email_from. With a custom domain, set CRONICLE_base_app_url to https://YOUR-DOMAIN. Jobs run inside the Cronicle container, which includes curl and ps.
Why Deploy Cronicle on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Cronicle on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content