Adds boot proxy to overcome Heroku timeouts #1
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
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.
Sometimes reaction takes too much time to start and Heroku thinks that there's a problem with your app. To sidestep this
we have a simple proxy that answers every request until it's ready.
It accepts the following environment variables:
USE_BOOT_PROXY: SetUSE_BOOT_PROXY=1to enable it. It's disabled by default.PING_PATH: The route we use to test if your app is ready. Defaults to/. You need to add a leading slash.PING_INTERVAL: Interval between probes, in seconds. Defaults to 1 second.BOOT_TIMEOUT: Maximum time to wait for your app in seconds. Defaults to 3600 (1 Hour). If reached we exit with anerror.