public
Description: A rails plugin that allows migrations to be stored in multiple locations
Homepage: http://multiple_migration_paths.zilkey.com
Clone URL: git://github.com/zilkey/multiple_migration_paths.git
updated docs
zilkey (author)
Sun Apr 27 07:43:49 -0700 2008
commit  f7902cbc7aaa11c7e123465540a532de70b1cbe8
tree    1917c35a3edd1b2d537f58a0507ac3eeca4e09f6
parent  51e3af2ef1516b988e474ab2e837fa5cef23890e
0
...
6
7
8
9
 
 
 
 
 
10
11
12
...
33
34
35
36
 
 
 
37
38
39
...
6
7
8
 
9
10
11
12
13
14
15
16
...
37
38
39
 
40
41
42
43
44
45
0
@@ -6,7 +6,11 @@ NOTE: this has only been tested with edge rails, post 2.0
0
 
0
 Make sure you are edge rails, then:
0
 
0
- script/plugin install ...
0
+ script/plugin install git://github.com/zilkey/multiple_migration_paths.git
0
+
0
+You may also need to add it to the front of your plugins path like so:
0
+
0
+ config.plugins = [ :multiple_migration_paths, :all ]
0
 
0
 == Summary
0
 
0
@@ -33,7 +37,9 @@ In this case, migrations would be run in the following order:
0
 * your/plugin_migrations/20080427101308_fourth.rb (it's the first chronologically, even though it's named "fourth")
0
 * migrate/20080427101407_first.rb
0
 * migrate/20080427101408_second.rb
0
-* migrate/20080427101409_third.rb
0
+* migrate/20080427101409_third.rb <- note that this comes from the migrate directory because the migrate directory comes before the your_plugin_migrations directory
0
+
0
+db/migrate is hard-coded to come before anything you add.
0
 
0
 What happens if you add a migration that comes chronologically before the last one? Rails automatically picks it up for you - so no worries!
0
   

Comments

    No one has commented yet.