Feat: support for laravel preview environment (feature testing) #536
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aagjalpankaj
force-pushed
the
laravel-preview-environment
branch
from
a3ab995 to
fe9c9d2
Compare
aagjalpankaj
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
serversideup/docker-phpimage can be used efficiently to test one feature at a time if we allowmigrate:fresh --seed.e.g. We have 3 environments:
Production(for the tag generated from main branch)Staging(for main branch)Testing(for feature branches)We use
Testingenvironment to deploy one feature at a time. But it creates incompatibility b/w the feature and database state. Because of that, we can't test features efficiently onTestingenvironment. Also, sometimes deployment fails and we need to reset the database manually.