Laravel recipe: Skip database tasks if .env is missing #3359
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug fix #…?
New feature?
BC breaks?
Tests added?
Docs added?
As discussed here with @peterjaap, database tasks could be omitted if the .env file is missing on the Laravel recipe.
Before:
php artisan migrate
=>Your .env file is empty! Skipping...
✅php artisan migrate:rollback
=> Crashes the deploy ❌After:
php artisan migrate
=>Your .env file is empty! Skipping...
✅php artisan migrate:rollback
=>Your .env file is empty! Skipping...
✅Let me know if you need me to add anything regarding documentation or tests.