dbhijacker 0.9.0 → 0.9.1

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    dbhijacker (0.9.0)
+    dbhijacker (0.9.1)
       rails (>= 2.3.14)
 
 GEM

data/README.rdoc

@@ -1,7 +1,14 @@
 Hijacker
 ========
 
-One application, multiple client databases. Although customizable, by default uses a combination of database and regular expression matching against the host domain to figure out which database to connect to.
+I don't recommend you use this gem. It is not production quality.
+
+Notes for adding thread safety:
+https://github.com/discourse/discourse/blob/691377b5af72ea0f3223223cfb623b991c96cbb8/vendor/gems/rails_multisite/lib/rails_multisite/connection_management.rb
+
+One application, multiple client databases. Although customizable, by default
+uses a combination of database and regular expression matching against the host
+domain to figure out which database to connect to.
 
 Example
 =======

data/dbhijacker.gemspec

@@ -3,7 +3,7 @@
 Gem::Specification.new do |s|
   s.name = %q{dbhijacker}
   s.homepage = "https://github.com/crystalcommerce/hijacker"
-  s.version = "0.9.0"
+  s.version = "0.9.1"
 
   s.license = "MIT"
 

data/lib/hijacker.rb

@@ -172,6 +172,11 @@ module Hijacker
     sister || master
   end
 
+  def self.do_hijacking?
+    (Hijacker.config[:hosted_environments] || %w[staging production]).
+      include?(ENV['RAILS_ENV'] || Rails.env)
+  end
+
   # just calling establish_connection doesn't actually check to see if
   # we've established a VALID connection. a call to connection will check
   # this, and throw an error if the connection's invalid. It is important 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: dbhijacker
 version: !ruby/object:Gem::Version
-  version: 0.9.0
+  version: 0.9.1
   prerelease: 
 platform: ruby
 authors: