Schema difference management between production and development environments

Asked 2 years ago, Updated 2 years ago, 57 views

In PHP: I would like to have the schema of the table changed in the development environment be reflected programmably in the production environment. What kind of management do you recommend? As I use PHP Ravel, I understand that it should be managed by a migration file, but I thought there was no other way.

Do people who use full-stack frameworks such as Rails and Ravel manage them properly with migration files?

php laravel

2022-09-30 20:28

2 Answers

If the ORM library that comes with the framework, such as Ravel, comes with a migration tool, it is often used.

Programmable application of this migration to the production environment can be handled with custom commands or subcommands for the framework with modern deployment tools.


2022-09-30 20:28

For Rails only, I would like to add an answer.

Rails leaves it entirely to the migration file (db/migrate/below) unless something serious happens. That's how the Rails exist.


2022-09-30 20:28

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.