Re: [Edgex-devel] Docker-compose on the remote server
Dell Customer Communicationtoggle quoted messageShow quoted text
We had an extremely old and outdated docker-compose.yaml in the /edgex-go/docker directory and we fielded many questions from people who were new to EdgeX about why our compose file didn't work. It turned out they were all attempting to raise the containers from this old, outdated file.
From this we learned that the first thing many users will do in order to take EdgeX for an initial spin is cd into /edgex-go/docker and execute "docker-compose up". We put the mechanism in there to load the latest release docker-compose.yaml via curl so that the users would be able to easily load up the latest release. If they want to then tweak the file to use local images, that will be easy now that they have the file locally.
With regard to proposing changes to the compose file, that should be easy enough since the location is in the docker-launch.sh script. From there the user can see the appropriate repo against which to submit a PR.
From: EdgeX-Devel@... [mailto:EdgeX-Devel@...] On Behalf Of Drasko DRASKOVIC
Sent: Thursday, July 12, 2018 6:14 PM
To: edgex-devel@...; edgex-golang@...
Subject: [Edgex-devel] Docker-compose on the remote server
what's the main purpose of keeping the docker-compose.yaml on the remote server (https://raw.githubusercontent.com/edgexfoundry/developer-scripts/master/compose-files/docker-compose-california-0.6.0.yml)?
It is obscuring the code/deployment, it is unclear form pure observation of the code what is being run. Moreover, it is getting harder to run and fine-tune the composition. If someone want to propose changes to the docker-compose, how is this done, when file is not in the VCS?
Mainflux Author and Technical Advisor
www.mainflux.com | Industrial IoT Cloud
Engineering Division | Paris, France