ejhayes_standalone_migrations 2.2.0

data/.travis.yml

@@ -0,0 +1,5 @@
+language: ruby
+rvm:
+  - 1.9.3
+  - 1.9.2
+script: bundle exec rake specs:travis

data/Gemfile

@@ -0,0 +1,12 @@
+source 'https://rubygems.org'
+
+gem 'rake', '~> 10.0'
+gem 'activerecord', ENV['AR'] || '~> 3.2'
+gem 'railties', ENV['AR'] || '~> 3.2'
+
+group :dev do
+  gem 'sqlite3'
+  gem 'rspec', '~>2'
+  gem 'jeweler'
+end
+

data/Gemfile.lock

@@ -0,0 +1,113 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    actionpack (3.2.13)
+      activemodel (= 3.2.13)
+      activesupport (= 3.2.13)
+      builder (~> 3.0.0)
+      erubis (~> 2.7.0)
+      journey (~> 1.0.4)
+      rack (~> 1.4.5)
+      rack-cache (~> 1.2)
+      rack-test (~> 0.6.1)
+      sprockets (~> 2.2.1)
+    activemodel (3.2.13)
+      activesupport (= 3.2.13)
+      builder (~> 3.0.0)
+    activerecord (3.2.13)
+      activemodel (= 3.2.13)
+      activesupport (= 3.2.13)
+      arel (~> 3.0.2)
+      tzinfo (~> 0.3.29)
+    activesupport (3.2.13)
+      i18n (= 0.6.1)
+      multi_json (~> 1.0)
+    addressable (2.3.6)
+    arel (3.0.2)
+    builder (3.0.4)
+    diff-lcs (1.1.3)
+    erubis (2.7.0)
+    faraday (0.8.9)
+      multipart-post (~> 1.2.0)
+    git (1.2.6)
+    github_api (0.10.2)
+      addressable
+      faraday (~> 0.8.7)
+      hashie (>= 1.2)
+      multi_json (~> 1.4)
+      nokogiri (~> 1.6.0)
+      oauth2
+    hashie (2.1.1)
+    highline (1.6.21)
+    hike (1.2.1)
+    i18n (0.6.1)
+    jeweler (2.0.1)
+      builder
+      bundler (>= 1.0)
+      git (>= 1.2.5)
+      github_api
+      highline (>= 1.6.15)
+      nokogiri (>= 1.5.10)
+      rake
+      rdoc
+    journey (1.0.4)
+    json (1.7.7)
+    jwt (0.1.11)
+      multi_json (>= 1.5)
+    mini_portile (0.5.3)
+    multi_json (1.7.1)
+    multi_xml (0.5.5)
+    multipart-post (1.2.0)
+    nokogiri (1.6.1)
+      mini_portile (~> 0.5.0)
+    oauth2 (0.9.3)
+      faraday (>= 0.8, < 0.10)
+      jwt (~> 0.1.8)
+      multi_json (~> 1.3)
+      multi_xml (~> 0.5)
+      rack (~> 1.2)
+    rack (1.4.5)
+    rack-cache (1.2)
+      rack (>= 0.4)
+    rack-ssl (1.3.3)
+      rack
+    rack-test (0.6.2)
+      rack (>= 1.0)
+    railties (3.2.13)
+      actionpack (= 3.2.13)
+      activesupport (= 3.2.13)
+      rack-ssl (~> 1.3.2)
+      rake (>= 0.8.7)
+      rdoc (~> 3.4)
+      thor (>= 0.14.6, < 2.0)
+    rake (10.2.2)
+    rdoc (3.12.2)
+      json (~> 1.4)
+    rspec (2.7.0)
+      rspec-core (~> 2.7.0)
+      rspec-expectations (~> 2.7.0)
+      rspec-mocks (~> 2.7.0)
+    rspec-core (2.7.1)
+    rspec-expectations (2.7.0)
+      diff-lcs (~> 1.1.2)
+    rspec-mocks (2.7.0)
+    sprockets (2.2.2)
+      hike (~> 1.2)
+      multi_json (~> 1.0)
+      rack (~> 1.0)
+      tilt (~> 1.1, != 1.3.0)
+    sqlite3 (1.3.6)
+    thor (0.17.0)
+    tilt (1.3.6)
+    tzinfo (0.3.37)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  activerecord (~> 3.2)
+  jeweler
+  railties (~> 3.2)
+  rake (~> 10.0)
+  rspec (~> 2)
+  sqlite3

data/LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2008-2011 Todd Huss
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.markdown

@@ -0,0 +1,265 @@
+Rails migrations in non-Rails (and non Ruby) projects.
+
+WHAT'S NEW
+==========
+In the 2.x release we have moved to using Rails 3 migrations instead of maintaining our own migration related code. Just about anything you can do with Rails 3 migrations you can now do with [Standalone Migrations](https://github.com/thuss/standalone-migrations) too! This removed 95% of the code we have to maintain. Big thanks to [Ricardo Valeriano](http://ricardovaleriano.com/) and [Michael Grosser](http://pragmatig.wordpress.com) for undertaking this major rewrite!
+
+CONTRIBUTE
+==========
+[Standalone Migrations](https://github.com/thuss/standalone-migrations) relies on the contributions of the open-source community! To submit a fix or an enhancement fork the repository, checkout the *develop* branch, make your changes, add your name to the *Contributors* section in README.markdown, and send us a pull request! If you're active and do good work we'll add you as a collaborator!
+
+USAGE
+=====
+Install Ruby, RubyGems and a ruby-database driver (e.g. `gem install mysql`) then:
+
+    $ gem install standalone_migrations
+
+Add to `Rakefile` in your projects base directory:
+
+```ruby
+require 'standalone_migrations'
+StandaloneMigrations::Tasks.load_tasks
+```
+
+Add database configuration to `db/config.yml` in your projects base directory e.g.:
+
+    development:
+      adapter: sqlite3
+      database: db/development.sqlite3
+      pool: 5
+      timeout: 5000
+
+    production:
+      adapter: mysql
+      encoding: utf8
+      reconnect: false
+      database: somedatabase_dev
+      pool: 5
+      username: root
+      password:
+      socket: /var/run/mysqld/mysqld.sock
+
+    test: &test
+      adapter: sqlite3
+      database: db/test.sqlite3
+      pool: 5
+      timeout: 5000
+
+### To create a new database migration:
+
+    rake db:new_migration name=foo_bar_migration
+    edit db/migrate/20081220234130_foo_bar_migration.rb
+
+#### If you really want to, you can just execute raw SQL:
+
+```ruby
+def up
+  execute "insert into foo values (123,'something');"
+end
+
+def down
+  execute "delete from foo where field='something';"
+end
+```
+
+### To apply your newest migration:
+
+    rake db:migrate
+
+### To migrate to a specific version (for example to rollback)
+
+    rake db:migrate VERSION=20081220234130
+
+### To migrate a specific database (for example your "testing" database)
+
+    rake db:migrate DB=test ... or ...
+    rake db:migrate RAILS_ENV=test
+
+### To execute a specific up/down of one single migration
+
+    rake db:migrate:up VERSION=20081220234130
+
+### To revert your last migration
+
+    rake db:rollback
+
+### To revert your last 3 migrations
+
+    rake db:rollback STEP=3
+
+### Custom configuration
+
+By default, Standalone Migrations will assume there exists a "db/"
+directory in your project. But if for some reason you need a specific
+directory structure to work with, you can use a configuration file
+named .standalone_migrations in the root of your project containing
+the following:
+
+```yaml
+db:
+    seeds: db/seeds.rb
+    migrate: db/migrate
+    schema: db/schema.rb
+config:
+    database: db/config.yml
+```
+
+These are the configurable options available. You can omit any of
+the keys and Standalone Migrations will assume the default values. 
+
+### on_loaded callbacks
+
+If you would like to use an external library such as [foreigner](https://github.com/matthuhiggins/foreigner) with standalone migrations, you can add the following to your `Rakefile`:
+
+```ruby
+require 'foreigner'
+
+StandaloneMigrations.on_load do
+  Foreigner.load
+end
+```
+
+###Multiple database support
+
+####Structure
+
+Create a custom configuration file for each database and name them `.database_name.standalone_migrations`. The same conditions apply as described under Custom Configuration, however you are most likely want to specify all options to avoid conflicts and errors.
+
+An example set up would look like this:
+
+```
+app/
+|-- db/
+|   |-- migrate/
+|   |   |-- db1/
+|   |   |   |-- 001_migration.rb
+|   |   |   
+|   |   |-- db2/
+|   |       |-- 001_migration.rb
+|   |    
+|   |-- config_db1.yml
+|   |-- config_db2.yml
+|   |-- seeds_db1.rb
+|   |-- seeds_db2.rb
+|   |-- schema_db1.rb
+|   |-- schema_db2.rb
+|
+|-- .db1.standalone_migrations
+|-- .db2.standalone_migrations
+```
+Sample config file:
+
+```yaml
+db:
+    seeds: db/seeds_db1.rb
+    migrate: db/migrate/db1
+    schema: db/schema_db1.rb
+config:
+    database: db/config_db1.yml
+```
+Of course you can achieve a different layout by simply editing the paths.
+
+#####Running
+
+You can run the Rake tasks on a particular database by passing the `DATABASE` environment variable to it:
+
+    $ rake DATABASE=db1 db:version
+
+Combined with the environment selector:
+
+    $ rake DATABASE=db2 DB=production db:migrate
+
+#### Changing environment config in runtime
+
+If you are using Heroku or have to create or change your connection
+configuration based on runtime aspects (maybe environment variables),
+you can use the `StandaloneMigrations::Configurator.environments_config`
+method. Check the usage example:
+
+```ruby
+require 'tasks/standalone_migrations'
+
+StandaloneMigrations::Configurator.environments_config do |env|
+
+  env.on "production" do
+
+    if (ENV['DATABASE_URL'])
+      db = URI.parse(ENV['DATABASE_URL'])
+      return {
+        :adapter  => db.scheme == 'postgres' ? 'postgresql' : db.scheme,
+        :host     => db.host,
+        :username => db.user,
+        :password => db.password,
+        :database => db.path[1..-1],
+        :encoding => 'utf8'
+      }
+    end
+
+    nil
+  end
+
+end
+```
+
+You have to put this anywhere on your `Rakefile`. If you want to
+change some configuration, call the #on method on the object
+received as argument in your block passed to ::environments_config
+method call. The #on method receives the key to the configuration
+that you want to change within the block. The block should return
+your new configuration hash or nil if you want the configuration
+to stay the same.
+
+Your logic to decide the new configuration need to access some data
+in your current configuration? Then you should receive the configuration
+in your block, like this:
+
+```ruby
+require 'tasks/standalone_migrations'
+
+StandaloneMigrations::Configurator.environments_config do |env|
+
+  env.on "my_custom_config" do |current_custom_config|
+    p current_custom_config
+    # => the values on your current "my_custom_config" environment
+    nil
+  end
+
+end
+```
+
+#### Exporting Generated SQL
+
+If instead of the database-agnostic `schema.rb` file you'd like to
+save the database-specific SQL generated by the migrations, simply
+add this to your `Rakefile`.
+
+```ruby
+require 'tasks/standalone_migrations'
+ActiveRecord::Base.schema_format = :sql
+```
+
+You should see a `db/structure.sql` file the next time you run a
+migration.
+
+Contributors
+============
+ - [Todd Huss](http://gabrito.com/)
+ - [Michael Grosser](http://pragmatig.wordpress.com)
+ - [Ricardo Valeriano](http://ricardovaleriano.com/)
+ - [Two Bit Labs](http://twobitlabs.com/)
+ - [ClassMonkeys](http://www.classmonkeys.com/) 
+ - [Windandtides](http://windandtides.com/)
+ - [Eric Lindvall](http://bitmonkey.net)
+ - [Steve Hodgkiss](http://stevehodgkiss.com/)
+ - [Rich Meyers](https://github.com/richmeyers)
+ - [Wes Bailey](http://exposinggotchas.blogspot.com/)
+ - [Robert J. Berger](http://blog.ibd.com/)
+ - [Federico Builes](http://mheroin.com/)
+ - [Gazler](http://blog.gazler.com/)
+ - [Yuu Yamashita](https://github.com/yyuu)
+ - [Koen Punt](http://www.koen.pt/)
+ - [Parker Moore](http://www.parkermoore.de/)
+ - [Marcell Jusztin](http://www.morcmarc.com)
+ - [Eric Hayes](http://ejhay.es)
+
+This work is originally based on [Lincoln Stoll's blog post](http://lstoll.net/2008/04/stand-alone-activerecord-migrations/) and [David Welton's post](http://journal.dedasys.com/2007/01/28/using-migrations-outside-of-rails).

data/Rakefile

@@ -0,0 +1,52 @@
+require 'rubygems'
+require 'bundler/setup'
+
+task :default do
+  sh "rspec spec"
+end
+
+task :all do
+  sh "AR='~>3.0.0' bundle update activerecord && bundle exec rake"
+  sh "AR='~>3.1.0.rc4' bundle update activerecord && bundle exec rake"
+end
+
+task :specs => ["specs:nodb"]
+namespace :specs do
+  require 'rspec/core/rake_task'
+
+  desc "only specs that don't use database connection"
+  RSpec::Core::RakeTask.new "nodb" do |t|
+    t.pattern = "spec/standalone_migrations/**/*_spec.rb"
+  end
+
+  desc "run all specs for travis"
+  RSpec::Core::RakeTask.new "travis" do |t|
+    t.pattern = "spec/**/*_spec.rb"
+    t.rspec_opts = "--tag ~@travis_error"
+  end
+
+  desc "run all specs including those which uses database"
+  task :all => [:default, :nodb]
+end
+
+# rake install -> install gem locally (for tests)
+# rake release -> push to github and release to gemcutter
+# rake version:bump:patch -> increase version and add a git-tag
+begin
+  require 'jeweler'
+rescue LoadError => e
+  $stderr.puts "Jeweler, or one of its dependencies, is not available:"
+  $stderr.puts "#{e.class}: #{e.message}"
+  $stderr.puts "Install it with: sudo gem install jeweler"
+else
+  Jeweler::Tasks.new do |gem|
+    gem.name = 'ejhayes_standalone_migrations'
+    gem.summary = "A thin wrapper to use Rails Migrations in non Rails projects"
+    gem.email = "thuss@gabrito.com"
+    gem.homepage = "http://github.com/thuss/standalone-migrations"
+    gem.authors = ["Todd Huss", "Michael Grosser"]
+    gem.license = "MIT"
+  end
+
+  Jeweler::GemcutterTasks.new
+end