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>

home/src/main/resources/config/example.runtime.properties

@@ -19,6 +19,26 @@
 # BASIC PROPERTIES
 # -----------------------------------------------------------------------------
 
+  #
+  # 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/
+  #
+Vitro.defaultNamespace = http://vivo.mydomain.edu/individual/
+
+  #
+  # 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.
+  #
+rootUser.emailAddress = vivo_root@mydomain.edu
+
 #
 # Argon2 password hashing parameters for time, memory and parallelism required to
 # compute a hash.