updating DB and picklebase on server start #695
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
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.
This does a background update of the database and the picklebase when the server starts, provided the UPDATE_ON_START env var is set to 1. That var is really just a proxy for "are we running on heroku?"
The reason we need to update when the server starts, instead of running a cron job, is that heroku wipes out the filesystem, and with it the picklebase, whenever the server restarts. The server automatically restarts every 24 hours, so that's a convenient time to update the database as well.
Once this is merged to
dev, we can do a push tomaster.UPDATE:
I tweaked the backend workflow a bit to (hopefully) make the registry publishing work correctly.
devbranchAny questions? See the getting started guide