que-scheduler 1.0.2 → 1.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 308f6550dbe058549d79ccf73b5a7ff5752d43a0
-  data.tar.gz: 8f003e7a8b2a39c6c205f7f137365a80b7c70992
+SHA256:
+  metadata.gz: b868cd1f3196296444a8927ad9c12f9e006b6c643033f96b93b61bf62ae871c3
+  data.tar.gz: 7367e82954c938a1ff1408dc65b8fd23042a88f0adbd9716e4763d43b6322bd4
 SHA512:
-  metadata.gz: 8d9dc59a505942c3427508dc6322acc174711fed650b6c771b783331ff00eb9077675284c698d54c8eaa6659e5882ff32efa180ceb2dc1aecbee0e7457363515
-  data.tar.gz: 7c0dd0d36ec8d585448b1dbfa7f4df3b50916baab0d8991a263cad81abef57ce242686f5f53589a18da9ed83e46705c03f40e800648f2566bc0c22f89506f750
+  metadata.gz: aaf6d2512f701f1eb526eb7a89b60108b80b355581a37d3b4b5bae1cbccd6829006cadd9dff45a692d51aba79530fd0d13af05f67c4afd46b35411f7ebce552d
+  data.tar.gz: 75901d2616803d878c81317b7d6b70919fef77303264d80ad264d7f362e0664df9772607c563c922380cd27792e7e38493d3b586e6479dac25e7f7aea00ed8ca

data/README.md

@@ -32,8 +32,9 @@ files, but with additional features.
 ## Schedule configuration
 
 The schedule file is a list of que job classes with arguments and a schedule frequency (in crontab 
-syntax). The format is a superset of the resque-scheduler config format, so it they can be used
-as-is with no modification, assuming the job classes are migrated from Resque to Que.
+syntax). The format is similar to the resque-scheduler config format, though priorities must be supplied as
+integers, and job classes must be migrated from Resque to Que. Cron syntax can be anything
+understood by [fugit](https://github.com/floraison/fugit#fugitcron).
 
 It has one additional feature, `schedule_type: every_event`. This is set on a job that must be run for every 
 single matching cron time that goes by, even if the system is offline over more than one match. To better process these `every_event` jobs, they are always enqueued with the first 
@@ -65,6 +66,10 @@ SendOrders:
   cron: "0 0 * * *"
   args: ['open']
   
+# Use simpler cron syntax.
+SendBilling:
+  cron: "@daily"
+
 # Altogether now
 all_args_job:
   cron: "0 0 * * *"
@@ -125,6 +130,10 @@ then reschedules itself. The flow is as follows:
 1. Some time later it runs again. It knows what jobs it should be monitoring, and notices that some have are due. It enqueues those jobs and then itself. Repeat.
 1. After a deploy that changes the config, the job notices any new jobs to schedule, and knows which ones to forget. It does not need to be re-enqueued or restarted.
 
-## Thanks
+## Inspiration
 
 This gem was inspired by the makers of the excellent [Que](https://github.com/chanks/que) job scheduler gem. 
+
+## Contributors
+
+* @jish

data/lib/que/scheduler/version.rb

@@ -1,5 +1,5 @@
 module Que
   module Scheduler
-    VERSION = '1.0.2'.freeze
+    VERSION = '1.0.3'.freeze
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: que-scheduler
 version: !ruby/object:Gem::Version
-  version: 1.0.2
+  version: 1.0.3
 platform: ruby
 authors:
 - Harry Lascelles
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-01-28 00:00:00.000000000 Z
+date: 2018-03-15 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -38,6 +38,20 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '3.10'
+- !ruby/object:Gem::Dependency
+  name: et-orbi
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">"
+      - !ruby/object:Gem::Version
+        version: 1.0.5
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">"
+      - !ruby/object:Gem::Version
+        version: 1.0.5
 - !ruby/object:Gem::Dependency
   name: fugit
   requirement: !ruby/object:Gem::Requirement
@@ -326,7 +340,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.6.14
+rubygems_version: 2.7.6
 signing_key: 
 specification_version: 4
 summary: A cron scheduler for Que