Feature/dockerize #1
Open
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.
Adds a Dockerfile and makes sure the application can be run both as a local development server and in a container. Checkout the README for detailed instructions.
This PR adds a working, Dockerized Flask-SocketIO server. In the future, this should handle pickled parse results made by the Minimalist Parser, and create visualizations for them, called 'Layouts'. For now, it just loads a standard pickle file (
standard.pickle) containing a dataset of 100 pre-parsed sentences, supplied by the researcher. This standard corpus is then turned into a displayable 'Layout', which is the default visualization used if the user simply wants to have an exploratory browse without any user input or parses.The main focus is here on getting a working Docker container. The main functionality (actually handling user-provided parses) is added in future PRs.