![critical ops mod 0.9.2 critical ops mod 0.9.2](https://i.ytimg.com/vi/N55RXpO48HI/maxresdefault.jpg)
The hostname of your SMTP server, for sending mail. The e-mail address to use as the "From" address when sending out notifications. This is used in e-mails to create self-referencing URLs. At the very least, you should set these properties: KeyĪ fully-qualified URL to Cronicle on your server, including the http_port if non-standard. You'll likely want to customize a few configuration parameters in the /opt/cronicle/conf/config.json file before proceeding. If this is your first time installing, please read the Configuration section first. Replace v1.0.0 with the desired Cronicle version from the release list, or master for the head revision (unstable). Once you have Node.js LTS installed, type this as root:Ĭurl -L | tar zxvf -strip-components 1 Cronicle may not work on the "current" release channel. Please note that we only support the Active LTS versions of Node.js. You'll also need to have Node.js LTS pre-installed on your server. Please note that Cronicle currently only works on POSIX-compliant operating systems, which basically means Unix/Linux and OS X. 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. API Keys for authenticating remote apps.Ī quick introduction to some common terms used in Cronicle: Term.Simple REST API for scheduling and running events.Web hooks for external notification systems.
![critical ops mod 0.9.2 critical ops mod 0.9.2](https://playsposter.com/wp-content/uploads/2020/08/Coloring-Fashion-Nail-Salon-MOD-APK.png)
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.
![critical ops mod 0.9.2 critical ops mod 0.9.2](https://1.bp.blogspot.com/-dMF_-LT6Qfs/WeazBFdU61I/AAAAAAAABd4/5rY12wpk7nUOfV2_UKJZOxbQ2YIp2xWeQCLcBGAs/s1600/1508290677232_1.jpg)
It handles both scheduled, repeating and on-demand jobs, targeting any number of worker servers, with real-time stats and live log viewer. OverviewĬronicle is a multi-server task scheduler and runner, with a web based front-end UI. Then start them all up again, and finally re-enable the scheduler.
CRITICAL OPS MOD 0.9.2 UPGRADE
So, it is recommended that you first disable the main scheduler on your master server (checkbox in top-right corner of the UI), wait for all jobs to complete, then shut down all servers and upgrade them all together. They all have to be on v0.8 or they all have to be on v0.9. Since this is a breaking API change for them, you cannot run "mixed" server clusters with some servers on Cronicle v0.8 and others on v0.9. We had to upgrade this dependency due to high severity vulnerabilities. In v0.9 we have upgraded to socket.io v4.4, which is incompatible with socket.io v1.7.3 that previous Cronicle versions used. For those upgrading multi-server clusters from Cronicle v0.8 to v0.9, you must upgrade all of your servers for them to be able to communicate.