
In plain words
A migration is like a recipe card for the database: "make a table called lessons with a title and a level". Anyone who runs the recipe gets the same result, on a laptop or a server, and the recipes run in order, by the date in their file names.
In Laravel
Migrations live in database/migrations. php artisan migrate runs every one that has not run yet; php artisan migrate:status shows which have. Commit migrations to Git with your code, so the code and the database always match.
See Build a REST API.

Every lesson stays free. Tap the thumbs up so we know what works, or say thanks with a soda or a coffee: it pays for hosting and new lessons.


