Replace the GitHub with a managed heroku proxy #2469
Merged
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
We sometimes hit the GitHub API rate limit. To get around this we have a hosted reverse proxy that has a baked in auth token. We occasionally have issue with the proxy going down, and can only wait for it to be bumped. This PR uses a proxy deployed on heroku with a very restrictive auth token. This should put an end to the proxy going down, and make it possible for multiple people to manage the server if needed.
mgreter
pushed a commit
to mgreter/libsass
that referenced
this pull request
Oct 6, 2017
We sometimes hit the GitHub API rate limit. To get around this we have a hosted reverse proxy that has a baked in auth token. We occasionally have issue with the proxy going down, and can only wait for it to be bumped. This PR uses a proxy deployed on heroku with a very restrictive auth token. This should put an end to the proxy going down, and make it possible for multiple people to manage the server if needed.
mgreter
pushed a commit
to mgreter/libsass
that referenced
this pull request
Oct 6, 2017
We sometimes hit the GitHub API rate limit. To get around this we have a hosted reverse proxy that has a baked in auth token. We occasionally have issue with the proxy going down, and can only wait for it to be bumped. This PR uses a proxy deployed on heroku with a very restrictive auth token. This should put an end to the proxy going down, and make it possible for multiple people to manage the server if needed.
xzyfer
added a commit
that referenced
this pull request
Oct 9, 2017
We sometimes hit the GitHub API rate limit. To get around this we have a hosted reverse proxy that has a baked in auth token. We occasionally have issue with the proxy going down, and can only wait for it to be bumped. This PR uses a proxy deployed on heroku with a very restrictive auth token. This should put an end to the proxy going down, and make it possible for multiple people to manage the server if needed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We sometimes hit the GitHub API rate limit. To get around this we
have a hosted reverse proxy that has a baked in auth token. We
occasionally have issue with the proxy going down, and can only wait
for it to be bumped.
This PR uses a proxy deployed on heroku with a very restrictive auth
token. This should put an end to the proxy going down, and make it
possible for multiple people to manage if needed.