Vladimir Rybas wrote: > 1. I usually put my db/schema.rb to .gitignore. There's some rake task > to > create your database not from migrations, but from schema.rb. But I > didn't > see anybody alive doing this.
I do it. > So, you don't really need this file in > your > repo. Completely wrong. You should always create your new installations' databases with rake db:schema:load , *never* by running migrations from zero. Migrations are only for changing *existing* installations, not for creating new ones from scratch. Therefore, you need db/schema.rb in version control. There's even a comment in that file that says as much. config/database.yml shouldn't be in version control because it contains passwords, but I like to put a sample version of that file (without passwords) in the repository as an example of how it should be set up. > > 2. You run your new migrations as soon as you get them. So, after > pulling > new changes from remote branch Right. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
