apartment 0.22.0 → 0.22.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 633c827866f4356529e375c9fe6b1b2f8886dbf3
-  data.tar.gz: 8b568ba43bbc49eb726ecc439b314b9c19c73ff3
+  metadata.gz: 0d86514c4d6c5f8dce97d40d42fb15b0728c1899
+  data.tar.gz: 896a629874de7e38e011439aecedc8a9d1e421e3
 SHA512:
-  metadata.gz: 96084d067de04ce41892a639887c7ce2d248e556c1624879721f0bf4529348cf504f04c408f7f82a6cbb17366078d48b542bf75f5b569cd32f85b684ff380739
-  data.tar.gz: 1173968bbe02e081870bba50bbbab33775e16a6f42e213b34bb15b0a47929fe1d8dcc8ca83eca243669ded99a8dd9a52d1cf46e49d995fb62209b0f877d71336
+  metadata.gz: 1748af36194e004026605133a90b994668b0abff22a2d0daeeef284cdf331491befc373aa6a498a20467ba7e97bf1644572b91d7183965ca550369f590801ddb
+  data.tar.gz: c746e001bce3d931773a929134162fc5c80ec915623cdc04371beeef19ce26b12bc079e3ed27013d0ddbca32f09469dfd5774ea439648ee1865996f3b50d981b

data/HISTORY.md

@@ -1,3 +1,10 @@
+# 0.22.1
+  * August 21, 2013
+
+  - Fix bug where if your ruby process importing the database schema is run
+    from a directory other than the app root, Apartment wouldn't know what
+    schema_migrations to insert into the database (Rails only)
+
 # 0.22.0
   * June 9, 2013
 

data/README.md

@@ -191,6 +191,20 @@ schema_search_path: "public,hstore"
 
 This would be for a config with `default_schema` set to `public` and `persistent_schemas` set to `['hstore']`
 
+Another way that we've successfully configured hstore for our applications is to add it into the
+postgresql template1 database so that every db that gets created has it by default.
+
+You can do so using a command like so
+
+```bash
+psql -U postgres -d template1 -c "CREATE SCHEMA hstore AUTHORIZATION some_username;"
+psql -U postgres -d template1 -c "CREATE EXTENSION IF NOT EXISTS hstore SCHEMA hstore;"
+```
+
+The *ideal* setup would actually be to install `hstore` into the `public` schema and leave the public
+schema in the `search_path` at all times. We won't be able to do this though until public doesn't
+also contain the tenanted tables, which is an open issue with no real milestone to be completed.
+Happy to accept PR's on the matter.
 
 ### Managing Migrations
 

data/lib/apartment/adapters/postgresql_adapter.rb

@@ -73,7 +73,7 @@ module Apartment
       #
       def connect_to_new(database = nil)
         return reset if database.nil?
-        raise ActiveRecord::StatementInvalid.new unless Apartment.connection.schema_exists? database
+        raise ActiveRecord::StatementInvalid.new("Could not find schema #{database}") unless Apartment.connection.schema_exists? database
 
         @current_database = database.to_s
         Apartment.connection.schema_search_path = full_search_path

data/lib/apartment/railtie.rb

@@ -16,6 +16,8 @@ module Apartment
         config.prepend_environment = false
         config.append_environment = false
       end
+
+      ActiveRecord::Migrator.migrations_paths = Rails.application.paths['db/migrate'].to_a
     end
 
     #   Hook into ActionDispatch::Reloader to ensure Apartment is properly initialized

data/lib/apartment/version.rb

@@ -1,3 +1,3 @@
 module Apartment
-  VERSION = "0.22.0"
+  VERSION = "0.22.1"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: apartment
 version: !ruby/object:Gem::Version
-  version: 0.22.0
+  version: 0.22.1
 platform: ruby
 authors:
 - Ryan Brunner
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-07-09 00:00:00.000000000 Z
+date: 2013-08-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord
@@ -54,15 +54,11 @@ files:
 - .ruby-gemset
 - .ruby-version
 - .travis.yml
-- .vagrant
-- Cheffile
-- Cheffile.lock
 - Gemfile
 - HISTORY.md
 - README.md
 - Rakefile
 - TODO.md
-- Vagrantfile
 - apartment.gemspec
 - circle.yml
 - lib/apartment.rb

data/.vagrant

@@ -1 +0,0 @@
-{"active":{"default":"c780c5fa-2739-4d9a-be05-2f4f6c1dcea6"}}

data/Cheffile

@@ -1,24 +0,0 @@
-#!/usr/bin/env ruby
-#^syntax detection
-
-site 'http://community.opscode.com/api/v1'
-
-# cookbook 'chef-client'
-
-# cookbook 'apache2', '>= 1.0.0'
-
-cookbook 'apt'
-cookbook 'build-essential'
-cookbook 'openssl'
-
-cookbook 'postgresql'
-cookbook 'mysql'
-
-cookbook 'git'
-
-cookbook 'rvm',
-  :git => 'https://github.com/fnichol/chef-rvm'
-
-# cookbook 'postgresql',
-#   :git => 'https://github.com/findsyou/cookbooks',
-#   :ref => 'postgresql-improvements'

data/Cheffile.lock

@@ -1,43 +0,0 @@
-SITE
-  remote: http://community.opscode.com/api/v1
-  specs:
-    apt (1.9.0)
-    build-essential (1.3.4)
-    chef_gem (0.0.5)
-    chef_handler (1.1.4)
-    dmg (1.1.0)
-    git (2.3.0)
-      build-essential (>= 0.0.0)
-      dmg (>= 0.0.0)
-      runit (~> 1.0)
-      windows (>= 0.0.0)
-      yum (>= 0.0.0)
-    mysql (2.1.2)
-      build-essential (>= 0.0.0)
-      openssl (>= 0.0.0)
-    openssl (1.0.2)
-    postgresql (2.2.2)
-      openssl (>= 0.0.0)
-    runit (1.1.0)
-      build-essential (>= 0.0.0)
-    windows (1.8.4)
-      chef_handler (>= 0.0.0)
-    yum (2.1.0)
-
-GIT
-  remote: https://github.com/fnichol/chef-rvm
-  ref: master
-  sha: 37ae6f0d6540ebc95d22004d68dd45fe304d7255
-  specs:
-    rvm (0.9.1)
-      chef_gem (>= 0.0.0)
-
-DEPENDENCIES
-  apt (>= 0)
-  build-essential (>= 0)
-  git (>= 0)
-  mysql (>= 0)
-  openssl (>= 0)
-  postgresql (>= 0)
-  rvm (>= 0)
-

data/Vagrantfile

@@ -1,112 +0,0 @@
-# -*- mode: ruby -*-
-# vi: set ft=ruby :
-
-Vagrant::Config.run do |config|
-  # All Vagrant configuration is done here. The most common configuration
-  # options are documented and commented below. For a complete reference,
-  # please see the online documentation at vagrantup.com.
-
-  # Every Vagrant virtual environment requires a box to build off of.
-  config.vm.box = "precise32-12.04"
-
-  # The url from where the 'config.vm.box' box will be fetched if it
-  # doesn't already exist on the user's system.
-  config.vm.box_url = "http://files.vagrantup.com/precise32.box"
-
-  # Boot with a GUI so you can see the screen. (Default is headless)
-  # config.vm.boot_mode = :gui
-
-  # Assign this VM to a host-only network IP, allowing you to access it
-  # via the IP. Host-only networks can talk to the host machine as well as
-  # any other machines on the same network, but cannot be accessed (through this
-  # network interface) by any external networks.
-  # config.vm.network :hostonly, "192.168.33.10"
-
-  # Assign this VM to a bridged network, allowing you to connect directly to a
-  # network using the host's network device. This makes the VM appear as another
-  # physical device on your network.
-  # config.vm.network :bridged
-
-  # Forward a port from the guest to the host, which allows for outside
-  # computers to access the VM, whereas host only networking does not.
-  # config.vm.forward_port 80, 8080
-
-  # Share an additional folder to the guest VM. The first argument is
-  # an identifier, the second is the path on the guest to mount the
-  # folder, and the third is the path on the host to the actual folder.
-  # config.vm.share_folder "v-data", "/vagrant_data", "../data"
-
-  # Enable provisioning with chef solo, specifying a cookbooks path, roles
-  # path, and data_bags path (all relative to this Vagrantfile), and adding
-  # some recipes and/or roles.
-  #
-  config.vm.provision :chef_solo do |chef|
-    chef.cookbooks_path = "cookbooks"
-
-    # chef.roles_path     = "recipes/roles"
-  #   chef.data_bags_path = "../my-recipes/data_bags"
-    chef.add_recipe "apt"
-
-    chef.add_recipe "mysql"
-    chef.add_recipe "mysql::server"
-    chef.add_recipe "postgresql"
-    chef.add_recipe "postgresql::server"
-
-    chef.add_recipe "rvm::vagrant"
-    chef.add_recipe "rvm::user"
-    chef.add_recipe "git"
-    # chef.add_role "web"
-  #
-  #   # You may also specify custom JSON attributes:
-    chef.json = {
-      mysql: {
-        version: '5.5',
-        server_root_password: "",
-        server_repl_password: "",
-        server_debian_password: ""
-      },
-      postgresql: {
-        version: '9.1',
-        password: {
-          postgres: ''
-        },
-        pg_hba: [
-          {type: 'local', db: 'all', user: 'all', addr: nil, method: 'trust'},
-          {type: 'host', db: 'all', user: 'all', addr: '127.0.0.1/32', method: 'trust'},
-          {type: 'host', db: 'all', user: 'all', addr: '::1/128', method: 'trust'}
-        ]
-      },
-      rvm: {
-        user_default_ruby: 'ruby-1.9.3-p392',
-        user_installs: [{
-          user: 'vagrant',
-          default_ruby: 'ruby-1.9.3-p392@apartment',
-          versions: %w{1.9.3-p392}
-        }]
-      }
-    }
-  end
-
-  # Enable provisioning with chef server, specifying the chef server URL,
-  # and the path to the validation key (relative to this Vagrantfile).
-  #
-  # The Opscode Platform uses HTTPS. Substitute your organization for
-  # ORGNAME in the URL and validation key.
-  #
-  # If you have your own Chef Server, use the appropriate URL, which may be
-  # HTTP instead of HTTPS depending on your configuration. Also change the
-  # validation key to validation.pem.
-  #
-  # config.vm.provision :chef_client do |chef|
-  #   chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
-  #   chef.validation_key_path = "ORGNAME-validator.pem"
-  # end
-  #
-  # If you're using the Opscode platform, your validator client is
-  # ORGNAME-validator, replacing ORGNAME with your organization name.
-  #
-  # IF you have your own Chef Server, the default validation client name is
-  # chef-validator, unless you changed the configuration.
-  #
-  #   chef.validation_client_name = "ORGNAME-validator"
-end