Docker Build & Dependency Upgrade #28
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.
I'm still genuinely interested in Pikes as a knowledge extraction suite to create RDF from text. As far as I know, I did not find a fitting replacement, which is why I tried to set it up.
During that time, I encountered many issues, which I tried to resolve during the way (some hacky things had to be done, like fixing the DBpedia API URI), but I finally got to a state where I could build Pikes and it runs fully.
I provided my steps as a Docker build (#3) and a dev environment so that it can be easily run in the future and Pikes can be easily set up.
Hopefully, this can be used as a base to enhance the functionality and performance.
Open for a review to remove the oddities I probably brought in and optimize the build (many steps are necessary right now).