Creating services in production and production-like environments

Since a service is created only once and updated whenever some of its aspects change (example:new image with the new release), there is no strong incentive to add service creation to the Continuous Deployment flow. All we'd get is increased complexity without any tangible benefit. Therefore, we'll create all the services manually and, later on, discuss how to automate the flow that will be triggered with each new release.

We already created go-demo, go-demo-db, proxy, jenkins, and registry services quite a few times so we'll skip the explanation and run scripts/dm-swarm-services-2.sh (https://github.com/vfarcic/cloud-provisioning/blob/master/scripts/dm-swarm-services-2.sh) that will recreate the situation we had in the previous chapters:

scripts/dm-swarm-services-2.sh

eval $(docker-machine env swarm-1)

docker service ls

The output of the service ls command is as follows (IDs are removed for brevity):

NAME       MODE       REPLICAS...