![]() ![]() Passwords are salted and hashed with bcrypt.Īny executable script in any language, which runs a job and reads/writes JSON to communicate with Cronicle. Remotely trigger jobs, etc.Ī human user account, which has a username and a password. The primary server which keeps time and runs the scheduler, assigning jobs to other servers, and/or itself.Ī worker server which will automatically become primary and take over duties if the current primary dies.Ī server which sits idle until it is assigned jobs by the primary server.Ī named group of servers which can be targeted by events, and tagged as "primary eligible", or "worker only".Ī special key that can be used by external apps to send API requests into Cronicle. The Cronicle documentation is split up across these files:Ī quick introduction to some common terms used in Cronicle: Term API Keys for authenticating remote apps.Simple REST API for scheduling and running events.Web hooks for external notification systems.Simple JSON messaging system for Plugins.Historical stats with performance graphs.Track CPU and memory usage for each job.Optionally queue up long-running events.Plugins can be written in any language.Real-time job status with live log viewer. ![]() You can give it simple shell commands, or write Plugins in virtually any language. It's basically a fancy Cron replacement written in Node.js. It handles both scheduled, repeating and on-demand jobs, targeting any number of worker servers, with real-time stats and live log viewer. Cronicle is a multi-server task scheduler and runner, with a web based front-end UI. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |