Remove VIVO configuration mechanism that never takes effect

..because it is overwritten by files in `example-config`

Resolves: vivo-community#8

README.md

@@ -23,7 +23,7 @@ Regardless of the usage, you will need to build the images, which require the fo
 
 ## VIVO Runtime Example
 
-The example [docker-compose.yml](docker-compose.yml) is a typical installation for trying out a simple VIVO installation in docker. This file starts three containers and uses the standard SDB system with the mariadb backend.  This example also shows how a local directory [example-config](example-config) is used to overwrite the default `runtime.properties` as installed by the Dockerfile.  Here the root password, and the domain are modified.
+The example [docker-compose.yml](docker-compose.yml) is a typical installation for trying out a simple VIVO installation in docker. This file starts three containers and uses the standard SDB system with the mariadb backend.  This example also shows how a local directory [example-config](example-config) is used to overwrite the default `runtime.properties` and `applicationSetup.n3` as installed by the Dockerfile.  Here the root password, and the domain are modified.
 
 ```bash
 docker-compose up -d

vivo/Dockerfile

@@ -32,8 +32,5 @@ RUN rm -r /usr/local/tomcat/webapps/examples
 # Set properties
 # Adjust logging, you can mount over this in docker-compose to further adjust
 COPY ./log4j.properties /usr/local/tomcat/webapps/VIVO/WEB-INF/classes
-WORKDIR /usr/local/VIVO/home/config
-COPY ./dockercompose.runtime.properties runtime.properties
-COPY ./example.applicationSetup.n3 applicationSetup.n3
 
 RUN export CATALINA_OPTS="-Xms512m -Xmx512m -XX:MaxPermSize=128m"