dev: add runproc tool for dev use cases #2080
Merged
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
m17ch
approved these changes
Jan 5, 2022
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.
Description:
This PR adds the
runproctool which is a simpler alternative to runjson that uses a Procfile-style input instead of JSON. This is intended to make it easier for devs to add extra commands (e.g. ngrok or sendit) and maintain. Additionally the output uses colored prefix and original output which should be a better experience.It also handles shutdown better/faster as well as the startup sequence lowering the amount of time a dev needs to wait.
Out of Scope
Only
make startis using the new tool currently.start-prodand the cypress test commands are untouched and will be updated in further PRs with additional testing & validation.