AgroPortal Docker

[syphax-bouazzouni]

Related to ontoportal/ontoportal-project#7

Goal

Run an ontoportal instance using docker

Requirments

• Have a CI to build the API docker image on each release (Feature: Add ontologies_api docker image build CI  ontoportal-lirmm/ontologies_api#58)
• Have a CI to build the UI docker image on each release (Feature: add local api tests CI ontoportal-lirmm/bioportal_web_ui#384)
• Have a CI to build the CRON docker image on each release (ontoportal-lirmm/ncbo_cron@e15e218)
• Have docker-compose to run the API (Feature: add ontoportal bash script ontoportal-lirmm/ontologies_api#59)
• Have docker-compose to run the UI (Feature: add local api tests CI ontoportal-lirmm/bioportal_web_ui#384)
• Have docker-compose to run the CRON (same as the API)
• Have a script/CLI to fetch and run the docker-compose together, running an Ontoportal instance, in API mode or UI mode. (Feature: Update ontoportal docker to use docker compose of the ui and api ontoportal/ontoportal_docker#7)
• Have a UI to bootstrap an ontoportal instance using Docker
  

[jonquet]

For this last point (UI) do you think about an independant small web app (ruby I assume) that would be deployed and stable somewhere and would be use to deploy Test/Stage/Agro ?

[imadbourouche]

For this last point (UI) do you think about an independant small web app (ruby I assume) that would be deployed and stable somewhere and would be use to deploy Test/Stage/Agro ?

A small simple web app using html and js where we can host it on github pages and will be used to:

• Choose docker version : BioPortal or AgroPortal (maybe will add Test/Stage/Master configuration)
• Select ontologies to import at start (example as we did for STY in our tests)
• Choose the mode run: UI or API, or Both
• Deploy the instance using this interface

And behind the scene it calls the ontoportal script that will do all this

[syphax-bouazzouni]

Close this iteration here, will reopen a new issue for the followup.