-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install Qanary using docker #20
Comments
Hello, I think I found the scripts in the Frankenstein repository. Frankenstein is a related project that also uses Qanary components. In this repository you can find both the start.sh and the initdb.sh scripts. I don't know why they are not on this repo. |
Thanks for your reply @jannlemm0913. I got the scripts there but faced some other problems along the way to build Qanary. So, just in case someone reads this, I gonna tell how I managed to make it work using docker. I started following the tutorial in the README and installed the core components of Qanary, which are in this repo. Then I cloned the repo Qanary-question-answering-components and, using mvn clean install, I installed all QA components. In this part I faced two problems:
Also, there are two things that weren't told in the tutorial. First is that you need to rename each component docker image name in the pom.xml. Also, for some reason, it must not contain any upper case letters. The second thing is that you need to build a stardog docker image. To do so, head to the repo Frankstein and inside the Qanary folder, there is a folder called stardog. In it you can find a README.md with instructions. Then I followed the rest of the tutorial and it work well. That's it to build Qanary. |
@mateusccoelho Thanks for sharing your experience. |
Hi, I'm trying to install Qanary with docker following the readme instructions. But I couldn't find any documentation about start.sh and initdb.sh scripts. I searched in Wiki and the source code but couldn't find anything.
Where do I get these scripts or configure them?
The text was updated successfully, but these errors were encountered: