Dockerization

[fabio.dibenedetto at consoft.it]

Hi all,
I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide.
In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you?

For what concern the documentation I updated the file modified by Pepe because there were some lost letters in some words and a wrong rst format in a little section. I added a webhook to our repository in order to have readthedocs automatically updated when you do some changes (I still haven't tried if it works, but I'll do when I'll commit the 'dist' folder)

Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it?

Fabio