If an event is set to run hourly, then a new job will be created every hour. Each event points to a Plugin, and a server or group to run it.Ī running instance of an event. The list of events, which are scheduled to run at particular times, on particular servers.Įvents can be assigned to categories which define defaults and optionally a color highlight in the UI.Īn entry in the schedule, which may run once or many times at any interval. 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
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |