Prepare app for production #6
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
The proliferation of conda DEBUG logs seems to cause a problem with certain installation environments. Reducing the loglevel to INFO should reduce and hopefully eliminate this issue.
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 PR updates the refdata so that the app may be registered in appdev. When registered in appdev, the refdata is downloaded to production and then subsequently copied to appdev. Therefore when
refdata-load.shruns it is using a production token which means that the production blobstore instance must be used. The conda logs loglevel has been set to INFO from DEBUG to avoid errors in the registration process. A few docstrings were not formatted properly and black complained, so I have included that change in this PR as well.