2018-04-23 10:02:51 +02:00
# -----------------------------------------------------------------------------
#
# Vitro runtime properties
#
# This file is provided as example.runtime.properties.
#
2019-04-25 14:51:38 -07:00
# Save a copy of this file as runtime.properties in your Vitro home directory,
2018-04-23 10:02:51 +02:00
# and edit the properties as needed for your installation.
#
# -----------------------------------------------------------------------------
2019-04-25 14:51:38 -07:00
#
2018-04-23 10:02:51 +02:00
# URL of Solr context used in local Vitro search. This will usually consist of:
# scheme + server_name + port + vitro_webapp_name + "solr"
# In the standard installation, the Solr context will be on the same server as Vitro,
# and in the same Tomcat instance. The path will be the Vitro webapp.name (specified
# above) + "solr"
# Example:
# vitro.local.solr.url = http://localhost:8080/vitrosolr
vitro.local.solr.url = http://localhost:8080/vitrosolr
#
2019-04-25 14:51:38 -07:00
# Email parameters which VIVO can use to send mail. If these are left empty,
2018-04-23 10:02:51 +02:00
# the "Contact Us" form will be disabled and users will not be notified of
# changes to their accounts.
#
email.smtpHost = smtp.my.domain.edu
email.replyTo = vivoAdmin@my.domain.edu
#
2019-04-25 14:51:38 -07:00
# The basic parameters for a MySQL database connection. Change the end of the
# URL to reflect your database name (if it is not "vitro"). Change the username
2018-04-23 10:02:51 +02:00
# and password to match the authorized user you created in MySQL.
#
VitroConnection.DataSource.url = jdbc:mysql://localhost/vitro
VitroConnection.DataSource.username = vitroweb
VitroConnection.DataSource.password = vitrovitro
#
# The maximum number of active connections in the database connection pool.
# Increase this value to support a greater number of concurrent page requests.
#
VitroConnection.DataSource.pool.maxActive = 40
#
# The maximum number of database connections that will be allowed
# to remain idle in the connection pool. Default is 25%
# of the maximum number of active connections.
#
VitroConnection.DataSource.pool.maxIdle = 10
#
2019-04-25 14:51:38 -07:00
# Parameters to change in order to use VIVO with a database other than
2018-04-23 10:02:51 +02:00
# MySQL.
#
VitroConnection.DataSource.dbtype = MySQL
VitroConnection.DataSource.driver = com.mysql.jdbc.Driver
VitroConnection.DataSource.validationQuery = SELECT 1
#
2018-05-18 16:40:08 +02:00
# Argon2 password hashing parameters for time, memory and parallelism required to
# compute a hash.
2018-04-23 10:02:51 +02:00
#
2018-05-18 16:40:08 +02:00
# A time cost defines the amount of computation realized and therefore the execution
# time, given in a number of iterations.
2018-04-23 10:02:51 +02:00
# A memory cost defines the memory usage, given in kibibytes
# A parallelism degree defines the number of parallel threads
2018-05-18 16:40:08 +02:00
# For determining the optimal values of the parameters for your setup please refer to
# the white paper section 9
# https://github.com/P-H-C/phc-winner-argon2/blob/master/argon2-specs.pdf
2018-04-23 10:02:51 +02:00
#
2018-05-09 13:51:11 +02:00
argon2.parallelism = 1
2018-04-23 10:02:51 +02:00
argon2.memory = 1024
argon2.time = 1000
#
2019-04-25 14:51:38 -07:00
# How is a logged-in user associated with a particular Individual? One way is
2018-04-23 10:02:51 +02:00
# for the Individual to have a property whose value is the username of the user.
# This is the name of that property.
#
selfEditing.idMatchingProperty = http://vitro.mydomain.edu/ns#networkId
#
# If an external authentication system like Shibboleth or CUWebAuth is to be
# used, these properties say how the login button should be labeled, and which
# HTTP header will contain the user ID from the authentication system. If such
2019-04-25 14:51:38 -07:00
# as system is not to be used, leave these commented out. Consult the
# installation instructions for more details.
2018-04-23 10:02:51 +02:00
#
#externalAuth.buttonText = Log in using BearCat Shibboleth
2019-04-25 14:51:38 -07:00
#externalAuth.netIdHeaderName = remote_userID
2018-04-23 10:02:51 +02:00
#
# Types of individual for which we can create proxy editors.
# If this is omitted, defaults to http://www.w3.org/2002/07/owl#Thing
proxy.eligibleTypeList = http://www.w3.org/2002/07/owl#Thing
#
2019-04-25 14:51:38 -07:00
# Show only the most appropriate data values based on the Accept-Language
2018-04-23 10:02:51 +02:00
# header supplied by the browser. Default is false if not set.
#
# RDFService.languageFilter = true
#
2019-04-25 14:51:38 -07:00
# Tell VIVO to generate HTTP headers on its responses to facilitate caching the
# profile pages that it creates.
2018-04-23 10:02:51 +02:00
#
2019-04-25 14:51:38 -07:00
# For more information, see
2018-04-23 10:02:51 +02:00
# https://wiki.duraspace.org/display/VIVO/Use+HTTP+caching+to+improve+performance
#
# Developers will likely want to leave caching disabled, since a change to a
2019-04-25 14:51:38 -07:00
# Freemarker template or to a Java class would not cause the page to be
2018-04-23 10:02:51 +02:00
# considered stale.
#
# http.createCacheHeaders = true
#
2019-04-25 14:51:38 -07:00
# Force VIVO to use a specific language or Locale instead of those
# specified by the browser. This affects RDF data retrieved from the model,
2018-04-23 10:02:51 +02:00
# if RDFService.languageFilter is true. This also affects the text of pages
2019-04-25 14:51:38 -07:00
# that have been modified to support multiple languages.
2018-04-23 10:02:51 +02:00
#
# languages.forceLocale = en_US
#
# A list of supported languages or Locales that the user may choose to
# use instead of the one specified by the browser. Selection images must
2019-04-25 14:51:38 -07:00
# be available in the i18n/images directory of the theme. This affects
# RDF data retrieved from the model, if RDFService.languageFilter is true.
# This also affects the text of pages that have been modified to support
# multiple languages.
2018-04-23 10:02:51 +02:00
#
# This should not be used with languages.forceLocale, which will override it.
#
# languages.selectableLocales = en, es, fr
2019-08-02 12:20:15 -05:00
# Triple pattern fragments is a very fast, very simple means for querying a triple store.
# The triple pattern fragments API in VIVO puts little load on the server, providing a simple means for getting data from the triple store. The API has a web interface for manual use, can be used from the command line via curl, and can be used by programs.
# tpf.activeFlag = true