"Gustavo de Sá Carvalho Honorato" <gustavohonorato wrote in post
"Gustavo de S Carvalho Honorato" <gustavohonorato wrote in post
> What are the good practices to deploy an Rails database in production?
> It is
> said that is unsafe to run database migrations in a production database,
That's ridiculous. Where did you get that information?
Yes, I agree with you. It's very strange, but I saw this information in
comments of generated schema.rb.
You're misinterpreting those comments.
# This file is auto-generated from the current state of the database.
Instead of editing this file,
# please use the migrations feature of Active Record to incrementally
your database, and
# then regenerate this schema definition.
In other words, don't edit this file manually; let the schema dumper do
# Note that this schema.rb definition is the authoritative source for
database schema. If you need
# to create the application database on another system,
Note: *create* the application DB, not *update* it.
you should be
db:schema:load, not running
# all the migrations from scratch.
Note: *from scratch*. This only applies when you are creating the DB
for the first time.
The latter is a flawed and
approach (the more migrations
# you'll amass, the slower it'll run and the greater likelihood for
That is correct.
# It's strongly recommended to check this file into your version control
There is nothing here about not using migrations on the production
database once it's been created.