Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upDockerization of Scholia #966
Comments
Daniel-Mietchen
added this to To do
in 1. Back-end development and testing with pilot corpora
via automation
This comment has been minimized.
This comment has been minimized.
|
Do you want help with this? I could imagine having one Dockerfile that just runs the server, then you could have configuration to point it at any given Wikidata SPARQL instance. This could also be orchestrated with docker-compose |
This comment has been minimized.
This comment has been minimized.
|
Help is always welcome. Perhaps start by checking what @nunogit is doing over at https://github.com/nunogit/scholia-docker . |
This comment has been minimized.
This comment has been minimized.
|
@cthoyt |
Pasting in some notes from various non-public channels to aid with documentation.
What we need is a combined container for a Scholia instance running on a stand-alone SPARQL endpoint whose timeouts and other configurations we control. Such an endpoint is included in the standard Wikibase Docker at https://github.com/wmde/wikibase-docker , which would be one way to go about this. Since we would want this endpoint to be synced to Wikidata (ideally in real time, though hourly or daily might be OK), we would have to look at
https://www.wikidata.org/wiki/Wikidata:Data_access
and especially
https://www.wikidata.org/wiki/Wikidata:Database_download
as well as existing tooling for handling dumps, e.g. as per
https://www.wikidata.org/wiki/Wikidata:Tools/For_programmers .
Most relevant here seems to be https://www.mediawiki.org/wiki/Wikidata_Toolkit .
Lots of good and bad dockerization out there - a well-documented example that I liked is
https://github.com/grafana/grafana/search?q=is%3Aopen+is%3Aissue+docker&unscoped_q=is%3Aopen+is%3Aissue+docker