A Laravel migration is stored in your application’s app/database/migrations folder. Each file deal with some set of chnages for the corresponding databases. Changes to the database are made in PHP rather than a database-specific flavour of SQL. Your PHP migration code ends up being converted into the DDL specific to your current database; this makes switching database platforms very easy. Since migrations are kept in their own directory, it’s pragmatic to include them into version control just like any other project code. Laravel migrations are run explicitly from command-line using the artisan tool.
Now we have to deal with migration:
We are going to use Laravel’s command line tool artisan to create our new migration. To run artisan you will need to open a terminal to the root of your Laravel application folder where the artisan script exists. The first thing we need to install the migration table, so that Laravel can keep track of which migrations have been run. Run below command to create the special table in database.
php artisan migrate:install
If success, artisan will respond with a message “Now we’re ready to do some migrating!” and you can see database table “migrations”. You don’t need to be overly concerned about the table. This is simply a table that helps Laravel to keep tabs on the migrations that you have and have not run. When you add new migrations, artisan migrate will check the migrationstable and execute all migrations that have not yet run.