VIVO-978 clarify the instructions for alternative triple stores
This commit is contained in:
parent
a7a894606b
commit
837d2afdad
2 changed files with 11 additions and 28 deletions
|
@ -70,21 +70,6 @@ VitroConnection.DataSource.dbtype = MySQL
|
|||
VitroConnection.DataSource.driver = com.mysql.jdbc.Driver
|
||||
VitroConnection.DataSource.validationQuery = SELECT 1
|
||||
|
||||
#
|
||||
# Optional URI of a SPARQL endpoint from which VIVO should display data.
|
||||
# If set, VIVO will use this endpoint as its triple store instead of the
|
||||
# SDB database.
|
||||
#
|
||||
#VitroConnection.DataSource.endpointURI =
|
||||
|
||||
#
|
||||
# Optional URI to use for modifying the above endpoint via SPARQL UPDATE.
|
||||
# This setting is only necessary if the endpoint does not support updates via
|
||||
# its main URI. (This may be done for access control purposes.)
|
||||
# If the endpointURI above is not set, this setting has no effect.
|
||||
#
|
||||
#VitroConnection.DataSource.updateEndpointURI =
|
||||
|
||||
#
|
||||
# The email address of the root user for the VIVO application. The password
|
||||
# for this user is initially set to "rootPassword", but you will be asked to
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue