About This Image
BrightstarDB is an open-source (MIT licensed) RDF triple store implented in C#. It provides a full REST API and .NET applications can also make use of it client library that provides advanced client-side functionality such as the ability to create C# "views" of RDF data and query them with LINQ. For more information about BrightstarDB please visit http://brightstardb.com/.
This image is based on the mono image which in turn is based on debian/wheezy.
How To Use This Image
If you want to run a single BrightstarDB database server you can download and run
our docker image from DockerHub with a single command:
docker run -d -t -p=80:8090 -v /brightstardata:/brightstardata brightstardb/brightstardb
Then browse to http://your.host.server/brightstar to start using the browser interface to the store.
Note that this image uses the default service configuration file that you can find in the
BrightstarService.exe.config). This configuration has no security configured for the
BrightstarDB endpoint, so be warned! This image is really intended for quick evaluation / experimentation
with BrightstarDB, not for production deployment.
Some notes on the command line
The -d and -t options just specify the mode that the container runs in, it will be run as a simple,
non-interactive container process.
The -v option maps the /brightstardata folder in the container to a folder on the host (in this
case a folder named /brightstardata) - docker will create this folder on the host if it does
not already exist.
The -p option maps BrightstarDB's default port of 8090 to the container port 80, this means
that once the container is running you should be able to connect to the BrightstarDB server
from a browser using the address http://your.host.server/brightstar/ (please note the /brightstar/
on the end of the URL!)
WARNING: Do not attempt to run multiple containers mapped to the same data folder. This will not work and you run the risk of corrupting the data contained in the BrightstarDB stores. Running multiple BrightstarDB containers on a single host is fine, as long as each container has its own dedicated data folder.