HTML pages in github

[Bollano Gianmario]

Hi Fabio,
it seems the trick of publishing HTML pages in github is using the special "gh-pages" branch.
Without that branch, github render any file as code instead of passing it to the browser.
instructions to commit html pages in a Github repository are here:
https://help.github.com/articles/creating-project-pages-manually/
or also here:
https://pages.github.com/

After committing in the gh-pages branch, the html pages should be visible as a web page.

Gianmario

-----Messaggio originale-----
Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it
Inviato: giovedì 24 settembre 2015 17:17
A: fiware-robotics at lists.fi-ware.org
Oggetto: [Fiware-robotics] R: Dockerization

Thank you for the link, but I'm having some troubles in updating the link because even if the html is in the repository I can go in that html but only in the source and this is not what we wanted. Does anyone know how to solve that?
For what concern the first point the 3 folders are because we don't distribute only one application, we have to distribute all we have and this means that we have 2 types of platforms (master and robot), 3 packages for the communication with fiware (firos, rcm_driver, robotics_msgs). The platforms are distributed without the other components and only in case of the 'all' folder we have a distribution with the master platform and the other packages inside it. These are all the distribution that we can provide using the script 'create_robotics_pkg'. If you use the sources, you have to take the sources and then run this script to create those distributions

-----Messaggio originale-----
Da: Bollano Gianmario [mailto:gianmario.bollano at telecomitalia.it] 
Inviato: giovedì 24 settembre 2015 16:26
A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org
Oggetto: R: Dockerization

Hi Fabio,
my answers:

1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders?
2) Fine. Any editing to improve/fix is absolutely welcomed.
3) OpenSpecs R4 are : http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4

Best,
Gianmario

-----Messaggio originale-----
Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it
Inviato: giovedì 24 settembre 2015 15:14
A: fiware-robotics at lists.fi-ware.org
Oggetto: [Fiware-robotics] Dockerization

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
_______________________________________________
Fiware-robotics mailing list
Fiware-robotics at lists.fiware.org
https://lists.fiware.org/listinfo/fiware-robotics-new

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

_______________________________________________
Fiware-robotics mailing list
Fiware-robotics at lists.fiware.org
https://lists.fiware.org/listinfo/fiware-robotics-new