landlady 0.0.3 → 0.0.4

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    OWMyZjZiZmY1OTY2NmM5ODRmMmM0Njg2ZmNlYmUzYzA4ZGU1NjcwYw==
+    ZmY3NzU1YzczZmRhYTY0ZTY5ZGQ5ZDZmZjFmOTY1YWE5MTlmNGE3Ng==
   data.tar.gz: !binary |-
-    ZjljNmE3N2JhYWIxYjI4MjZkZjkxYzgyNjgyYWUwZTRhZTNlNWJlYQ==
+    ODIxYjI0YWM2MTM5MmJjZDNjMTlhMGVhZTg3MTJmNDVmY2M4NjI3OQ==
 SHA512:
   metadata.gz: !binary |-
-    Mzg5ZDVlYmY2OTlmZmFjMjQ3OTk3MTA2ODI3NmE2ZmVjY2RmM2UzN2NkYzk1
-    ODE3Mjk3NGVlZTNiODg2OWM5MWE5ODA4OGVjNDY5OWE2OTdlODZiMjRiMDE3
-    MDdkMGQ5ZDQxMGM0ZTI0Y2I4OTZjOTY0ZmIzMGM5MzNjOWZjMGQ=
+    NGE2OTc5NGQzMGExNDdiYjc3MGYxOTM2Zjk2OGRjMWIwMDc2ODBlMzNiNGFk
+    OTNiMDc3M2ZmMGJlZDRlM2VkY2JjYzQ3ZmJjOWViZDAwZTBlNmZjNjgxNzA1
+    Njk0OGExZWJkZGVhOGJmMjQxMmZhNzk5YTZlODBiYmZjN2ZiZWQ=
   data.tar.gz: !binary |-
-    MWQ2NzE1NGU5ZGEwOGEyNGI1ZWU1YjRhYzFkMmZiMTVjODJhN2MwMmFlOWFj
-    ZGM4ZDE3ZjUxNGI2NDA1NGZmODkyZGYxOGM4NDBjZGI2NDk1NzI0MTBmMDQ0
-    MzdiMGVlODNlZDU3MDM5NzEyYmRiMTc3NTAxOGZkMGQ5NTE2MWU=
+    OGRiYjQyNjFhZmU3YmEwODYxODViOWY0YWI2OGVhMWQ2ODJlYWRkMzcwMGM3
+    YjI2MzJhMzI1NzE2YTg3MGFkOTk4ZmQyZTM0ZTAwNWNlZDc5NDFhZjQyZjli
+    ODA3MmNlYTFiYTlhMWE0MWY1MGIzZDJmMWZjNjRlNDg3YzE0MmI=

data/README.md

@@ -1,6 +1,8 @@
 # Landlady
 
-super easy postgres multitenancy
+Super Easy Postgres Multitenancy
+
+Using a subdomain mapping design pattern, Landlady takes advantage of PostgresQL SCHEMA_SEARCH_PATH and using naming conventions will map tenants with complete data segregation to the required data namespace.
 
 ## Installation
 
@@ -23,6 +25,11 @@ Then Install and run the migrations:
 
 
 ## Usage
+Landlady uses
+
+### Development Environments
+Once you have Tenants set up, use something like lvh.me to map back to localhost
+		$ i.e. http://tenant1.lvh.me
 
 ### Tenant migrations
 Landlady will set up Tenants, then because she is a good land lady will update each of the tenants with the required migrations with:

data/landlady.gemspec

@@ -8,7 +8,7 @@ Gem::Specification.new do |spec|
   spec.version       = Landlady::VERSION
   spec.authors       = ["Kym McInerney"]
   spec.email         = ["kym@holodigm.com.au"]
-  spec.description   = %q{Uses Postgres datbase name spacing to allow schema segregation multitenancy}
+  spec.description   = %q{Using a subdomain mapping design pattern, Landlady takes advantage of PostgresQL SCHEMA_SEARCH_PATH and using naming conventions will map tenants with complete data segregation to the required data namespace.}
   spec.summary       = %q{Super simple postgres multitenancy}
   spec.homepage      = ""
   spec.license       = "MIT"

data/lib/landlady/version.rb

@@ -1,3 +1,3 @@
 module Landlady
-  VERSION = "0.0.3"
+  VERSION = "0.0.4"
 end

data/lib/tasks/tenants.rake

@@ -6,7 +6,7 @@ namespace :tenants do
       ActiveRecord::Migration.verbose = verbose
 
       Tenant.all.each do |tenant|
-        puts "migrating tenant #{tenant.id} (#{tenant.subdomain})"
+        puts "Migrating tenant #{tenant.id} (#{tenant.subdomain})"
         Landlady.set_search_path tenant.id, false
         version = ENV["VERSION"] ? ENV["VERSION"].to_i : nil
         ActiveRecord::Migrator.migrate("db/migrate/", version)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: landlady
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
 platform: ruby
 authors:
 - Kym McInerney
@@ -38,7 +38,9 @@ dependencies:
     - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
-description: Uses Postgres datbase name spacing to allow schema segregation multitenancy
+description: Using a subdomain mapping design pattern, Landlady takes advantage of
+  PostgresQL SCHEMA_SEARCH_PATH and using naming conventions will map tenants with
+  complete data segregation to the required data namespace.
 email:
 - kym@holodigm.com.au
 executables: []