Move fakeapi server to heroku, separate repository #98
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
brettdh
force-pushed
the
heroku-fakeapi
branch
from
ace269f to
9bb5885
Compare
brettdh
force-pushed
the
heroku-fakeapi
branch
from
9bb5885 to
0011131
Compare
brettdh
force-pushed
the
heroku-fakeapi
branch
from
0011131 to
bff8228
Compare
brettdh
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.
Description
Fake API server is now deployed to heroku from a separate repository, theliturgists/fakeapi.
Motivation and Context
Currently, the fakeapi is deployed via now.sh 1.0, which has a massive cold start delay (over a minute). I tried moving to now 2.0, which seemed to have a far better cold start situation, but I ran into issues:
So, I'm trying out heroku. So far, startup time seems MUCH faster. 🎉