89f759fcbc
Split deploy.properties into build.properties and runtime.properties, with runtime.properties going into the Vitro home directory. Modify ConfigurationProperties to locate the Vitro home directory, either by System property or JNDI Environment variable, or from build.properties, and to read from both build.properties and runtime.properties. Revise the install and upgrade documents for VIVO and Vitro. Change comments and error messages that referred to deploy.properties by name.
39 lines
1.3 KiB
Properties
39 lines
1.3 KiB
Properties
# -----------------------------------------------------------------------------
|
|
#
|
|
# VIVO build properties
|
|
#
|
|
# This file is provided as example.build.properties.
|
|
#
|
|
# Save a copy of this file as build.properties, and edit the properties as
|
|
# needed for your deployment.
|
|
#
|
|
# -----------------------------------------------------------------------------
|
|
|
|
#
|
|
# Where is the Vitro core directory?
|
|
# In most deployments, this is set to ./vitro-core (It is not uncommon for this
|
|
# setting to point elsewhere in development environments).
|
|
# Examples:
|
|
# vitro.core.dir = ./vitro-core
|
|
# vitro.core.dir = ../vitro
|
|
# vitro.core.dir = /usr/local/vitro/trunk
|
|
vitro.core.dir = ./vitro-core
|
|
|
|
#
|
|
# The base install directory for your Tomcat server. The VIVO application
|
|
# will be deployed in the /webapps directory below this base.
|
|
#
|
|
tomcat.home = /usr/local/tomcat
|
|
|
|
#
|
|
# The name of the VIVO application. This will be used as the name of the
|
|
# subdirectory within your Tomcat server's /webapps directory. It also appears
|
|
# in the URL for the application. For example, http://my.vivo.server/vivo
|
|
#
|
|
webapp.name = vivo
|
|
|
|
#
|
|
# The location where the VIVO application will store the data that it creates.
|
|
# This includes uploaded files (usually images) and the search index.
|
|
#
|
|
vitro.home = /usr/local/vivo/home
|