Thanks. In my original post I meant to link to Database migrations | Strapi Documentation but I put the : at the end of the URL instead of putting a space before the colon.
My guess is that something like this happens when the Strapi app starts. But I want more clarification:
- first it finds all of the migration files in ./database/migrations .
- Then it checks the database to see if any of those have not been run yet
- Any of those migration files for the current environment that haven’t been run yet gets run in alphabetical order. Only if automigration is turned on?
- Then – I think, but this part I’m fuzzy on – Strapi goes through and finds all of the schema .JSON files for “content-types” . Then it tries to modify the database tables to make sure that the tables support the schemas? Only if auto migration is turned on? But it doesn’t generate migration files for these changes to the database? They just sort of happen behind the scenes? I’m not sure yet. I haven’t had time to study Strapi enough yet.