| Package Data | |
|---|---|
| Maintainer Username: | erjanmx |
| Maintainer Contact: | erjanmx@gmail.com (Erjan) |
| Package Create Date: | 2017-12-20 |
| Package Last Update: | 2024-02-26 |
| Home Page: | |
| Language: | PHP |
| License: | MIT |
| Last Refreshed: | 2024-04-11 03:03:55 |
| Package Statistics | |
|---|---|
| Total Downloads: | 209,672 |
| Monthly Downloads: | 4,700 |
| Daily Downloads: | 205 |
| Total Stars: | 54 |
| Total Watchers: | 3 |
| Total Forks: | 8 |
| Total Open Issues: | 1 |
Laravel has a migrate:status command to check status of migrations. But this command mostly for humans. There are situations where one needs to know whether to run migrations when using autodeployment, maybe with switching to maintenance mode.
This package contains a migrate:check command that exits with non-zero code if there are any migrations to run.
This command supports all database drivers that Laravel does.
You can install the package via composer:
composer require erjanmx/laravel-migrate-check
Thanks to Laravel 5.5 package auto-discovery the migrate:check command will be registered
php artisan migrate:сheck
You can specify database and path to migration file via options just like they are used in php artisan migrate command
Please see CHANGELOG for more information what has changed recently.
In order for the test to be run you should set up an empty mysql database laravel_migrate_check . The username should be root, the required password should be empty.
$ composer test
Please see CONTRIBUTING for details.
The MIT License (MIT). Please see License File for more information.