Made TARGET_WAR_NAME configurable in build command

metincansiper · May 23, 2018 · 85c22dc · 85c22dc
1 parent dfc1f33
commit 85c22dc
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 1 deletion.
diff --git a/Dockerfile b/Dockerfile
@@ -6,5 +6,5 @@ RUN mvn clean install
 
 # deploy the war file created in build stage to tomcat
 FROM tomcat:7.0.86-jre8-alpine
-ENV TARGET_WAR_NAME=FactoidToBiopaxServer
+ARG TARGET_WAR_NAME=FactoidToBiopaxServer
 COPY --from=build /app/target/*.war /usr/local/tomcat/webapps/${TARGET_WAR_NAME}.war
diff --git a/README.md b/README.md
@@ -23,6 +23,9 @@ You can deploy the server to a docker container by following the steps below. "<
 docker build -f Dockerfile -t factoid-to-biopax .
 docker run -it --rm --name factoid-to-biopax --publish <PORT>:8080 factoid-to-biopax 
 ```
+
+To create the war file with another name than "FactoidToBiopaxServer"(war name affects where the service is deployed) add ``--build-arg TARGET_WAR_NAME=<WAR_NAME>`` to the build command.
+
 ## Consuming the Service
 
 After completing installation and deployment steps the server will be up and running at "http://localhost:8080/FriesToBiopaxServer" (You should update port number in case you use another one). You can send a post request to "http://localhost:8080/FactoidToBiopaxServer/ConvertToOwl" to consume the service.