multiverse 0.0.3 → 0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 564a47885d1668334ca29f1c0d036f8cfe03e850
-  data.tar.gz: 87575b3d26f533b2a53aebdeaa6138c499b75708
+  metadata.gz: 1a5b405124244211b42303192e0aeb223e64fe6f
+  data.tar.gz: dae706b36d5e653b9b3b3b150cbe715cb344ff55
 SHA512:
-  metadata.gz: a94499ae8268d11fb6a833e564cfb73b165800a7bf7f4cfdcc095f105ed2543f68125a7f22221b548240dbbe65d89e6bdeb89b6cc224da12124f8bd163827ffa
-  data.tar.gz: 1322982a75cd8f8c8e0bb0c0edbdf51361d47a40b7448ca95948021f5adfaf5cae6768a6525eee714bef755d23e04134700314152f17ab8ab6b335167db63d08
+  metadata.gz: 3043d8c0e5f12c3a8ef352b57dc46ba3bd686c3a5f4286957456c28005c07bd6d55827cb3c8010791740548f96971f5e6e069617ab36b9e5412ee8dadea61800
+  data.tar.gz: b8331d53ad7688b15a834d50a5fd0fcb7df408f4455f4386e5e2f549365cb0ab26d72ada5178bb2797392fe5a8c11b4a53dd6d7da707c06349c888ba053c63ac

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 0.1.0
+
+- Fixed test conf
+
 ## 0.0.3
 
 - Removed debug statement

data/README.md

@@ -18,13 +18,15 @@ gem 'multiverse'
 
 ## Getting Started
 
-Generate a new database
+In this example, we’ll have a separate database for our e-commerce catalog that we’ll call `catalog`.
+
+The first step is to generate the necessary files.
 
 ```sh
 rails generate multiverse:db catalog
 ```
 
-This generates `CatalogRecord` class for models to inherit from and adds configuration to `config/database.yml`. It also creates a `db/catalog` directory for migrations and `schema.rb` to live.
+This creates a `CatalogRecord` class for models to inherit from and adds configuration to `config/database.yml`. It also creates a `db/catalog` directory for migrations and `schema.rb` to live.
 
 `rails` and `rake` commands run for the original database by default. To run commands for the new database, use the `DB` environment variable. For instance:
 
@@ -93,6 +95,26 @@ And inside the `after_fork` block
 CatalogRecord.establish_connection :"catalog_#{Rails.env}"
 ```
 
+## Testing
+
+### Fixtures
+
+[Rails fixtures](http://guides.rubyonrails.org/testing.html#the-low-down-on-fixtures) work automatically.
+
+### Database Cleaner
+
+Database Cleaner supports multiple connections out of the box.
+
+```ruby
+cleaner = DatabaseCleaner[:active_record, {model: CatalogRecord}]
+cleaner.strategy = :transaction
+cleaner.cleaning do
+  # code
+end
+```
+
+[Read more here](https://github.com/DatabaseCleaner/database_cleaner#how-to-use-with-multiple-orms)
+
 ## History
 
 View the [changelog](https://github.com/ankane/multiverse/blob/master/CHANGELOG.md)

data/lib/generators/multiverse/db_generator.rb

@@ -19,7 +19,7 @@ module Multiverse
           production_conf = "database: db/#{lower_name}_production.sqlite3"
         else
           development_conf = "database: #{lower_name}_development"
-          test_conf = "database: #{lower_name}_development"
+          test_conf = "database: #{lower_name}_test"
           production_conf = "url: <%= ENV['#{lower_name.upcase}_DATABASE_URL'] %>"
         end
 

data/lib/multiverse/version.rb

@@ -1,3 +1,3 @@
 module Multiverse
-  VERSION = "0.0.3"
+  VERSION = "0.1.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: multiverse
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.1.0
 platform: ruby
 authors:
 - Andrew Kane
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2017-11-04 00:00:00.000000000 Z
+date: 2017-11-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails