Revert deployment strategy (#230)
* revert deployment changes * update docker and compose for previous deployment * minor readme update * use package instead of install this avoids exploding war file in tomcat but seems to be missing overlays for VIVO theme * test docker workflow * test deploy workflow * add package profile for home * skip deploy for installer * skip installer by profile * update workflows * minor readme update * use app-name for vivo log file name * Update log4j.properties Co-authored-by: William Welling <wwelling@library.tamu.edu>
This commit is contained in:
parent
47fb4fdc05
commit
d00d7de585
17 changed files with 359 additions and 168 deletions
|
@ -1,52 +1,9 @@
|
|||
<Context> <!-- useHttpOnly="false" -->
|
||||
|
||||
<!--
|
||||
# The 'home' property specifies the location of VIVO HOME.
|
||||
# The system user used to run the VIVO web application must have write access
|
||||
# to the parent directory of the directory defined in this property, if VIVO HOME
|
||||
# does not already exist.
|
||||
# If this directory already exists, the system user used to run the VIVO web application
|
||||
# must have write access to this directory.
|
||||
-->
|
||||
<Environment
|
||||
type="java.lang.String"
|
||||
name="vitro/home"
|
||||
value="${vivo-dir}" override="true"/>
|
||||
|
||||
<!--
|
||||
# The name of the application (possibly not used).
|
||||
-->
|
||||
<Environment
|
||||
type="java.lang.String"
|
||||
name="vitro/appName"
|
||||
value="${app-name}" override="true"/>
|
||||
|
||||
<!--
|
||||
# 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
|
||||
# change the password the first time you log in.
|
||||
-->
|
||||
<Environment
|
||||
type="java.lang.String"
|
||||
name="vitro/rootUserAddress"
|
||||
value="vivo_root@mydomain.edu" override="true"/>
|
||||
|
||||
<!--
|
||||
# This namespace will be used when generating URIs for objects created in the
|
||||
# editor. In order to serve linked data, the default namespace must be composed
|
||||
# as follows (optional elements in parentheses):
|
||||
#
|
||||
# scheme + server_name (+ port) (+ servlet_context) + "/individual/"
|
||||
#
|
||||
# For example, Cornell's default namespace is:
|
||||
#
|
||||
# http://vivo.cornell.edu/individual/
|
||||
-->
|
||||
<Environment
|
||||
type="java.lang.String"
|
||||
name="vitro/defaultNamespace"
|
||||
value="http://vivo.mydomain.edu/individual/" override="true"/>
|
||||
|
||||
<!-- Disable persist sessions on shut down.-->
|
||||
<Manager pathname="" />
|
||||
</Context>
|
||||
|
|
|
@ -24,7 +24,7 @@
|
|||
# debug.log4j.properties exists will be used instead, if it exists, but is not stored in Subversion.
|
||||
|
||||
log4j.appender.AllAppender=org.apache.log4j.RollingFileAppender
|
||||
log4j.appender.AllAppender.File= ${catalina.base}/logs/vivo.all.log
|
||||
log4j.appender.AllAppender.File=${catalina.base}/logs/${app-name}.all.log
|
||||
log4j.appender.AllAppender.MaxFileSize=10MB
|
||||
log4j.appender.AllAppender.MaxBackupIndex=10
|
||||
log4j.appender.AllAppender.layout=org.apache.log4j.PatternLayout
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue