The new init-dbs branch includes code that allows for databases to be initialized on startup. For example, if your use the following docker-compse file
Than any directories in the staging directory will be checked for databases and installed if they do not already exist. Any example directory would look like:
The config.ttl is the jena assembler file that is used to configure the database. It is copied into /fuseki/configurations/covid19.ttl file, (eg.) Directories are url encoded and treated as separate graphs, and added into those graph names using tdb2.tdbloader. Files ending in *.sparql-update are sent to the tdb2.update command.
This allows for sharing database initializations that include configuration for the fuseki database.
@jrmerz / @jtyzzer here is a new fuseki server that allows data installation on setup. There are a number of databases that can be added located in this Drive
We should be able to share fuseki tests more easily this way.
The new
init-dbs
branch includes code that allows for databases to be initialized on startup. For example, if your use the following docker-compse fileThan any directories in the
staging
directory will be checked for databases and installed if they do not already exist. Any example directory would look like:The config.ttl is the jena assembler file that is used to configure the database. It is copied into
/fuseki/configurations/covid19.ttl
file, (eg.) Directories are url encoded and treated as separate graphs, and added into those graph names usingtdb2.tdbloader
. Files ending in*.sparql-update
are sent to thetdb2.update
command.This allows for sharing database initializations that include configuration for the fuseki database.