backburner 1.6.0 → 1.6.1

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 93c9b77199209b894ae963d9474a3234212225021537f99b9fee11433e73f6c4
4
- data.tar.gz: 49e775e7a32ccc85a557f27ba89a146617553b45e0a252ddfe12f84d1e501706
3
+ metadata.gz: 49962267b79394b57f1c5adef6bee09e157b6739e6ef284b34f73de5a195bee8
4
+ data.tar.gz: 7f89821645420c0ec11592e3f11f1a9cfe1d4e088e6db4fcb4a84f338f3d4ca7
5
5
  SHA512:
6
- metadata.gz: f6e5cdea7a5e3092b8dfc61199ccabf1eb898b3eae4c5645171a7fecc415d7c1c467d1fd173d78732dee6c60bfd2f5928cb728a52e13269bbd951d6d304a2ceb
7
- data.tar.gz: e0da0a58b32ea88704e33a4e19a03b3f3b1c8cb63428091743953112841e6b2fc1bf27d5de18d51a8777cad9ee45e069a02a0f9cc132fdf8a0e036bd0379e162
6
+ metadata.gz: 65bf80745461e0d6402f549f5bcb6755435ccb97f77123686f338ec18ba0a9bc140e8bc321520d3fbf39feb302c705b3f163b8eb785f07a23688cb117a1abb8d
7
+ data.tar.gz: b1af70707c86341e342109e833c6b1d12fd5b47995be3f66efda319e433c9d2a3f7c0384f1ca562d8a598e7e1f08d08339c0a3714439838ffdf7851e05cdf07b
data/CHANGELOG.md CHANGED
@@ -1,5 +1,9 @@
1
1
  # CHANGELOG
2
2
 
3
+ ## Version 1.6.1 (Jan 16 2023)
4
+
5
+ * Change `File.exists?`` to `File.exist?` as latest ruby versions have removed support (@ShrutiSaagar).
6
+
3
7
  ## Version 1.6.0 (December 30 2021)
4
8
 
5
9
  * TBD (please help backfill)
data/README.md CHANGED
@@ -18,7 +18,7 @@ custom logging, and extensible plugin hooks.
18
18
 
19
19
  Backburner is well tested and has a familiar, no-nonsense approach to job processing, but that is of secondary importance.
20
20
  Let's face it, there are a lot of options for background job processing. [DelayedJob](https://github.com/collectiveidea/delayed_job),
21
- and [Resque](https://github.com/defunkt/resque) are the first that come to mind immediately. So, how do we make sense
21
+ and [Resque](https://github.com/resque/resque) are the first that come to mind immediately. So, how do we make sense
22
22
  of which one to use? And why use Backburner over other alternatives?
23
23
 
24
24
  The key to understanding the differences lies in understanding the different projects and protocols that power these popular queue
@@ -28,7 +28,7 @@ module Backburner
28
28
 
29
29
  def self.load_environment(file = nil, environment = nil)
30
30
  file ||= "."
31
- if File.directory?(file) && File.exists?(File.expand_path("#{file}/config/environment.rb"))
31
+ if File.directory?(file) && File.exist?(File.expand_path("#{file}/config/environment.rb"))
32
32
  ENV["RAILS_ENV"] = environment if environment && ENV["RAILS_ENV"].nil?
33
33
  require "rails"
34
34
  require File.expand_path("#{file}/config/environment.rb")
@@ -40,7 +40,7 @@ module Backburner
40
40
  $rails_rake_task = false
41
41
  ::Rails::Initializer.run :load_application_classes
42
42
  end
43
- elsif File.directory?(file) && File.exists?(File.expand_path("#{file}/config/boot.rb"))
43
+ elsif File.directory?(file) && File.exist?(File.expand_path("#{file}/config/boot.rb"))
44
44
  ENV["RACK_ENV"] = environment if environment && ENV["RACK_ENV"].nil?
45
45
  ENV["PADRINO_ROOT"] = file
46
46
  require File.expand_path("#{file}/config/boot.rb")
@@ -1,3 +1,3 @@
1
1
  module Backburner
2
- VERSION = "1.6.0"
2
+ VERSION = "1.6.1"
3
3
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: backburner
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.6.0
4
+ version: 1.6.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Nathan Esquenazi
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2021-12-30 00:00:00.000000000 Z
11
+ date: 2023-01-16 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: beaneater