This is just for the review wherein the deployment of chatbot related microservices are implemented, the complete pull request will come by preparing the ansible playbooks for deploying extraction team related microservices.
The changes implemented as part of this pull request are:
1) 2 playbooks are written
a) One to build docker images(This would be eventually replaced by automating the process with docker cloud.
b) To deploy the chatbot related microservices.
2) Modified the application.yml files of the microservices to use Environment variables for deployment and default values for developer systems.
By including the approach, we can get away from the maven profiles for docker and local. And this gives us more flexibilty during the runtime of the microservices. Since, the pom.xml is only available at compile time, and if we need to make some changes at runtime we would need to do a lot of workarounds.
For example, if you want to run the eureka-server on your local windows machine you can use the following command:
mvn clean spring-boot:run -P windows
If you want to build a Docker container from a microservice, use the following command:
You need to run this command on a linux machine
sudo mvn clean install dockerfile:build -P linux
To run a docker container use:
sudo docker run -p 8761:8761 -v /logs/:/logs -E -e EUREKA_SERVICE_HOST=hostname -f --net sask --name "eureka-server" -t dicegroup/sask-eureka
Should I be closing this pull request and re-open one later, as I'll be adding more commits and all would unnecessary notifications due to existing pull request
This is just for the review wherein the deployment of chatbot related microservices are implemented, the complete pull request will come by preparing the ansible playbooks for deploying extraction team related microservices.
The changes implemented as part of this pull request are: 1) 2 playbooks are written a) One to build docker images(This would be eventually replaced by automating the process with docker cloud. b) To deploy the chatbot related microservices.
2) Modified the application.yml files of the microservices to use Environment variables for deployment and default values for developer systems.
By including the approach, we can get away from the maven profiles for docker and local. And this gives us more flexibilty during the runtime of the microservices. Since, the pom.xml is only available at compile time, and if we need to make some changes at runtime we would need to do a lot of workarounds.
For example, if you want to run the eureka-server on your local windows machine you can use the following command:
mvn clean spring-boot:run -P windows
If you want to build a Docker container from a microservice, use the following command: You need to run this command on a linux machine sudo mvn clean install dockerfile:build -P linux
To run a docker container use: sudo docker run -p 8761:8761 -v /logs/:/logs -E -e EUREKA_SERVICE_HOST=
hostname -f
--net sask --name "eureka-server" -t dicegroup/sask-eurekaPlease review and share your comments.