Every repository with this icon (
Every repository with this icon (
| name | age | message | |
|---|---|---|---|
| |
MIT-LICENSE | Wed Dec 03 11:34:05 -0800 2008 | |
| |
README.markdown | Tue Jan 13 15:34:12 -0800 2009 | |
| |
Rakefile | Wed Dec 03 11:34:05 -0800 2008 | |
| |
init.rb | Wed Dec 03 12:37:23 -0800 2008 | |
| |
lib/ | Wed Dec 03 12:39:13 -0800 2008 | |
| |
tasks/ | Thu Feb 12 03:53:22 -0800 2009 | |
| |
test/ | Wed Dec 03 11:34:05 -0800 2008 |
DB_BRANCH
Rails plugin to play nice with git branching and databases. Loads a branch-specific database YAML file allowing you to migrate in branches without affecting the database of other branches.
More information:
http://sevenwire.com/blog/2008/12/03/introducing-db-branch.html
http://cryingwhilecoding.com/2009/1/11/easily-manage-db-changes-between-branches-in-git
Usage
First, you should have your db backed up. Just saying.
By default, it will run setup, config, and create_clone tasks so you'll end up with a running copy of your existing db for your branch
rake db:branch
Update the db again? The clone task will drop and recreate the db and reload it from the original
rake db:branch:clone
Just want a clean db without the data? create_empty will create the config and just load the db from the schema
rake db:branch:create_empty
No longer need the branched db? purge will remove the branched databases and config
rake db:branch:purge
Branch database config files are named database.branch.[branch_name].yml. The database names for the branch are renamed as [application]_[environment]_[branch] or [databasename]_[branch] if the originals where not named using a [application]_[environment] convention.
You can alter which database is used for the cloning or schema loading by setting the RAILS_ENV variable
rake db:branch:clone RAILS_ENV=development
But can it go to Eleven?
The only thing I can imagine making this any better is possibly finding a way of using gits hooks to automatically run rake db:branch when creating a new branch and rake db:branch:purge when deleting a branch. That'd be pretty hot.
Authors
Nate Sutton (nate@sevenwire.com)
Brandon Arbini (brandon@sevenwire.com)
Mike Vincent (mike@cryingwhilecoding.com)







