Draft
Conversation
Member
Author
|
This PR should not change the Docker image build, so the following error does not affect this PR at all However, I did notice a problem with the image build - filed this as a new issue: |
Member
Author
|
Don't merge until next week 🙏 hopefully product is public by then |
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
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.
Problem
CLEANDB-frontend prototype is currently publicly accessible
We would like this to be behind the same (temporary) auth wall that is currently used by OpenEnzymeDB
Approach
TODOs:
How to Test
NOT CURRENTLY DEPLOYED
Staging:
openenzymedb), you should be routed to the CLEANDB frontendopenenzymedb), you should be shown a 403: Forbidden error pageProduction:
openenzymedb), you should be routed to the CLEANDB frontendopenenzymedb), you should be shown a 403: Forbidden error page