Why migration:run throws error in production environment?

[Leko]

Hi there.

I think that migration should be the same on the production and development environment.
It is better approach to keep same schema definition between production and development.

But ./ace migration:run throws exception on NODE_ENV=production without --force flag.

https://github.com/adonisjs/adonis-lucid/blob/master/src/Commands/Run.js#L33

Why throws error in production environment?

Sorry for my English.

[thetutlage]

True, it is not safe to run migrations in production, as migrations can override data in your existing tables. Ace disables it by default and if you are sure that you want to run migrations than you can always use the --force flag

[Leko]

@thetutlage Thank you for your prompt response.

Please tell me good practice on production.

• Use --force flag? (not safe)
• Run the SQL(eg. CREATE TABLE ..., ALTER TABLE ...) manually?
• Something else?

[thetutlage]

Use the force flag, there is nothing wrong with it. It is there to make sure you are not running migration:run by mistake, which may end up in loosing important data. As long as you know what you are doing you can use --force and it's all good.

[Leko]

@thetutlage Thank you!