This is a set of exporatory informtion that was used to test QLEVER It now includes configuration files to deploy a qlever stack locally, and to portainer See the readme
This will provide a
- Qlever qlever-server-SOURCE
- Qlever-ui qlever-ui
- Petrimaps - mapping for Qlever GeoSPARQL qlever-petrimaps
if you are interested in Qlever and running it locally, see the readme in deployment
This will provide a
- Qlever localhost:7019
- Qlever-ui localhost:8176
- Petrimaps - mapping for Qlever GeoSPARQL localhost:9090
ADD MORE STUFF ABOUT HOW TO USE THIS.
So why does this repo exist? It is mostly to explore deploying Qlever via docker compose files for some of our workflows and automated approaches. In that case, qlever-control was not quite what was needed. So we basically decomposed qlever-control logic into docker compose files.
If you are interested in deploying Qlever leveraging Docker Compose and data volumes or interfaces such as Portainer, this repository may provide some use for you. Or you may provide us some insight (i.e., pull requests welcome).
You should go to the qlever-control repo instead. That is the official repo for a nice server and UI onboarding experience with Qlever. Also visit the main qlever repo or the Qlever Wiki.
If you are interested in these components, you should check them out directly at;
One other goal for this repository is to explore and refine the approach to sharing graphs as products for local use. Similar to the manner in which Parquet or Zarr files might be generated and shared as a data product, a Knoledge Graph (KG) can too.
The Qlever approach is to use a Qleverfile, and the development teams creation of the previously mentioned qlever-control makes this a solid approach to graph as a data product.
Graphs can be stored in compressed n-quads files, for example, in an object store and then referenced in a small Qleverfile for people to download and leverage for then fetching, indexing and querying the KG.