No doubt, the part that everyone wanted to see the most is where we actually give our application an actual spin. However, because it is a scheduler, we first need to prepare some configurations. We will use the following application configuration file:
job-scheduler { config-path="/etc/scheduler/conf.d" config-extension="json" workers=4 db { connection-string="jdbc:h2:mem:test;DB_CLOSE_DELAY=-1" username="" password="" }}
We will name our file production.conf and we will put it in /etc/scheduler/conf.d. Now we need to create some actual job configurations. We will have to put them where the config-path property is pointing to:
// ping.json{ "name": "Ping Command", "command": "ping google.com -c 10", "frequency": "Hourly", ...
