Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/atomgraph/fuseki-docker
Docker image for Apache Jena's Fuseki SPARQL endpoint
https://github.com/atomgraph/fuseki-docker
docker-image fuseki graph-store jena rdf sparql triplestore
Last synced: 2 months ago
JSON representation
Docker image for Apache Jena's Fuseki SPARQL endpoint
- Host: GitHub
- URL: https://github.com/atomgraph/fuseki-docker
- Owner: AtomGraph
- Created: 2018-12-23T18:30:00.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2022-10-21T18:30:27.000Z (over 2 years ago)
- Last Synced: 2024-04-16T18:33:31.654Z (9 months ago)
- Topics: docker-image, fuseki, graph-store, jena, rdf, sparql, triplestore
- Language: Shell
- Homepage: https://hub.docker.com/r/atomgraph/fuseki
- Size: 29.3 KB
- Stars: 12
- Watchers: 5
- Forks: 8
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# fuseki-docker
Docker image for Apache Jena's [Fuseki](https://jena.apache.org/documentation/fuseki2/) (v2) triplestore server
## Endpoints
In the following examples which use `/ds` as the dataset path, these main endpoints are available:
* http://localhost:3030/ds/sparql for SPARQL Query
* http://localhost:3030/ds/update for SPARQL Update
* http://localhost:3030/ds/data for Graph Store (read-write)
* http://localhost:3030/ds/get for Graph Store (read-only)
They can be redefined in [configuration](https://jena.apache.org/documentation/fuseki2/fuseki-configuration.html#defining-the-service-name-and-endpoints-available).
Post 3030 has to be [mapped](https://docs.docker.com/engine/reference/commandline/run/#publish-or-expose-port--p---expose) to be able to access it on the Docker host.
## Usage
Arguments after the image name (`atomgraph/fuseki`) become arguments to the [Fuseki server (no UI)](https://jena.apache.org/documentation/fuseki2/fuseki-main.html). As the name explains, this server version _does not include the user interface_.
### Examples
Empty memory dataset:
docker run --rm -p 3030:3030 atomgraph/fuseki --mem /ds
Dataset from file `data.nt` (which is mounted as part of the current directory):
docker run --rm -p 3030:3030 -v $(pwd):/usr/share/data atomgraph/fuseki --file=/usr/share/data/data.nt /ds
Help (all run options explained):
docker run --rm atomgraph/fuseki --help
## Profiling
Use `Dockerfile.profiler` to build the image instead of the default `Dockerfile`.
Then append the following settings to the `JAVA_OPTIONS` env variable:
```
-Dcom.sun.management.jmxremote=true \
-Djava.rmi.server.hostname=127.0.0.1 \
-Dcom.sun.management.jmxremote.host=0.0.0.0 \
-Dcom.sun.management.jmxremote.port=9991 \
-Dcom.sun.management.jmxremote.rmi.port=9991 \
-Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.registry.ssl=false \
-Dcom.sun.management.jmxremote.authenticate=false \
-Djava.net.preferIPv4Stack=true
```
and use [VisualVM](https://visualvm.github.io/) to create a JMX connection to `127.0.0.1:9991`. Only tested with VisualVM running on Windows 10 and the remote Fuseki app running in a Docker container on WSL2.