You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
php artisan vendor:publish --all will create a new migration files everytime it is deployed.
To Reproduce
1.use CI/CD to deploy laravel project
2. use command php artisan vendor:publish --all && php artisan migrate
3. you will get duplicate migration on each deployment
Expected behavior
Should have one set of migration upon deployment
Solution Ideas
Give date and time to migration, it should not have dynamic date and time
The text was updated successfully, but these errors were encountered:
@sundaramtalekar I think php artisan vendor:publish --all should run on your dev machine and then commit need files into git when CI/CD should be run php artisan migrate only.
php artisan vendor:publish --all will create a new migration files everytime it is deployed.
To Reproduce
1.use CI/CD to deploy laravel project
2. use command php artisan vendor:publish --all && php artisan migrate
3. you will get duplicate migration on each deployment
Expected behavior
Should have one set of migration upon deployment
Solution Ideas
Give date and time to migration, it should not have dynamic date and time
The text was updated successfully, but these errors were encountered: