forked from vivo-community/vivo-project-template
-
Notifications
You must be signed in to change notification settings - Fork 0
/
example.build.properties
51 lines (46 loc) · 1.67 KB
/
example.build.properties
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
# -----------------------------------------------------------------------------
#
# 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 VIVO core directory?
# In most deployments, this is the home directory
# Examples:
# vivo.core.dir = ../vivo
# vivo.core.dir = /usr/local/vitro/trunk
#nihvivo.dir = ../vivo-rel-1.2
nihvivo.dir = ./VIVO
#
# 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
#
# The base install directory for your Tomcat server. The VIVO application
# will be deployed in the /webapps directory below this base.
#
# creating a symbolic link to this tomcat home directory:
# $ ln -s ~/work/apache-tomcat-8.0.21 /usr/local/tomcat8
#
tomcat.home = /usr/local/tomcat8
#
# 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_project/home