Adding artisan migration helpers

[filpgame]

Adding Laravel's artisan migration helpers

Q	A
Bug fix?	no
New feature?	yes
BC breaks?	no
Deprecations?	no
Fixed tickets	n/a

[oanhnn]

Please edit comment and prepend table

Q	A
Bug fix?	no
New feature?	yes
BC breaks?	no
Deprecations?	no
Fixed tickets	n/a

Migartion should be executed without option --force

[antonmedv]

Agree, no --force.

[filpgame]

But without --force in production environment, the migration command will be canceled, cause the command asks for a confirmation

[antonmedv]

Is --force used only for asks for a confirmation? May be there is an not-interactive mode?

[philbates35]

Pretty sure all --force does is to automatically proceed when it asks for confirmation. @FlipGame is right, without it the command would be cancelled.

[barryvdh]

Agreed, you need --force.

Perhaps also add php artisan db:seed and a php artisan migrate:status to check before running migrate?

Not sure if it's possible to do the confirm on the Deployer side, to be safe?

[antonmedv]

It's possible, but what happens if you run php artisan migrate --force if there no migrations?

[philbates35]

It just says "nothing to migrate". Force is purely just to get past the "you're in production, are you you sure you want to do this?" prompt.

[antonmedv]

Do we need deploy:migrate in deploy task?

[barryvdh]

Do we need deploy:migrate in deploy task?
I wouldn't do that by default.

[oanhnn]

I think this problem will be resolved in #622
Thank you @filpgame about your contribution.