ruby-clock 2.0.0.beta10 → 2.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0f773f1b873c6048b24cb6c78769c809fd3008c0316463071633086aa572f853
-  data.tar.gz: 28de0953617822f2473cecebdac1ab308420231670073db0d4458d89d527e3ee
+  metadata.gz: 20fc4e914b706c818238f8d45a6d81ff650e18ae8fe90b47a9f818e28871bbc6
+  data.tar.gz: b0d23fded8dfd9981bedcfcaf9300376c615f53ce782a6f9e1a807b3e054c324
 SHA512:
-  metadata.gz: e4d94f375285033a0ca49ed535b29f0768adac1efa83f4c63a67090f866aa2a1f72b4a0159c746d99bf765c8c5b7f308daff090be0e2b671518d8fe67cf3b63e
-  data.tar.gz: 693519be98311aff6e24aae1c61cf908f710049a6854886264f100dc844f8436b3ba58f0ab1bd9b6d6a5bf3f5916383d744ce9390dbb582bdd70f4c6dab03936
+  metadata.gz: 840663b99bf1d803274dc28d7b72882958b1e99fd93b7039fe249192fcb510b07fd894b5e5b404de1153a53095763bd0aaaf1c0a16f20b225187477a3887fab9
+  data.tar.gz: 7ba7a882f7e6cb6ed115d88769d433d835e9b8782c5e9272436ff28956594cd9d8ae995ea54e59e86fbf3daf4848b0eca30a60b20933a16401d0f21cbb6e24a4

data/CHANGELOG.md

@@ -1,4 +1,4 @@
-## 2.0.0 beta
+## 2.0.0
 
 ### Features
 * The way the [rails app reloader](https://guides.rubyonrails.org/threading_and_code_execution.html)
@@ -30,7 +30,6 @@
 * Code reorganization so there are no unnecessary methods in top-level `Kernel` namespace
 * top-level DSL methods are now implemented with refinements, so they don't polute other code
 
-
 ### Migrating from ruby-clock version 1 to version 2
 * The minimum ruby version is 3.0
 * The top of every Clockfile must begin with `using RubyClock::DSL`
@@ -39,8 +38,8 @@
 * Your existing Clockfile with `schedule.foo` invocations will still work, but you now have the option to use
   `every`, `cron`, and `on_error` at the top-level, without referencing `schedule`.
 * You now have the option of catching and reporting errors encountered when parsing the Clockfile.
-* There is no longer a need to have a binstub in rails. You can delete bin/clock from your app.
 * remove the `posix-spawn` gem from your project
+* There is no longer a need to have a binstub in rails. You can delete bin/clock from your app.
 * The invocations (in Procfile, or wherever else you start ruby-clock) should change from
 
       bundle exec rails runner bin/clock

data/README.md

@@ -171,10 +171,18 @@ For your jobs with cron-style schedules, it will generate a dummy crontab file t
 For your jobs with "Every X seconds" schedules, a comment will be made in the file and they will not be vizualized.
 
 ```console
+## install go
+brew install go # homebrew
+sudo port install go # macports
+
+## install cronv https://github.com/takumakanari/cronv#go-install
+go install -v github.com/takumakanari/cronv/cronv@0.4.5
+
+## generate dummy crontab
 bundle exec clock --generate-dummy-crontab Clockfile ../clock/daily.rb ../clock/weekly.rb > dummycron.txt
 ## IMPORTANT: open dummycron.txt in an editor and remove the boot startup message cruft from the top
-cat dummycron.txt | /Users/your-username/go/bin/cronv -d 1d -o ./my_cron_schedule.html
-open dummycron
+cat dummycron.txt | ~/go/bin/cronv --duration=1d --title='Clock Jobs' --width=50 -o ./my_cron_schedule.html
+open my_cron_schedule.html
 ```
 
 ## More Config and Capabilities

data/lib/ruby-clock/version.rb

@@ -1,3 +1,3 @@
 class RubyClock
-  VERSION = "2.0.0.beta10"
+  VERSION = "2.0.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ruby-clock
 version: !ruby/object:Gem::Version
-  version: 2.0.0.beta10
+  version: 2.0.0
 platform: ruby
 authors:
 - John Bachir
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2023-06-25 00:00:00.000000000 Z
+date: 2023-08-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rufus-scheduler
@@ -272,9 +272,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: 3.0.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubygems_version: 3.3.7
 signing_key: