Start Guard instead of sleeping in dev environment #14887
Conversation
This file contains 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
top4ek
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.
Allow developers to start Guard inside backend-test container instead of sleeping. This allows to run tests automatically on source files change while existing testing method via
docker execstill can be used.Guard can be started by setting START_GUARD environment variable to "1". Otherwise it's behavior stayed the same.
Also, we can use docker attach and stop code with binding.break(tty and stdin options in compose files enabled).
And it's possible(not sure, as I didn't try) to use debugger gem's protocol to integrate with IDEs and test editors.