This Confluence wiki site, maintained by DuraSpace prior to the recent merger with LYRASIS, will transition from the duraspace.org domain to the lyrasis.org domain on Saturday, Nov 16 beginning at approximately 7pm ET. A period of downtime of 2-3 hours is expected. After the transition, this wiki will be available at https://wiki.lyrasis.org/. All links to duraspace.org wiki pages will be redirected to the correct lyrasis.org URL. If you have questions prior to or following the transition please contact: wikihelp@lyrasis.org.
Skip to end of metadata
Go to start of metadata

As a step towards modularizing and streamlining the deployment of the VIVO application, an initial set of components have been identified as appropriate to deploy in their own, separate Docker containers. 

  • Search index (Solr and/or ElasticSearch)
  • SDB database (MySQL)
  • The rest (core VIVO application)

The objective is to have a single Docker-Compose file that coordinates the deployment of the components above.

Requirements

  1. Core VIVO must be deployable as a Docker container
  2. VIVO's configuration files must be configurable at deploy-time (runtime.properties, applicationSetup.n3)
  3. VIVO's Solr must be deployable as a Docker container
  4. VIVO's ElasticSearch must be deployable as a Docker container
  5. VIVO's MySQL must be deployable as a Docker container
  6. VIVO's Docker container must be able to use the Dockerized Solr
  7. VIVO's Docker container must be able to use the Dockerized ElasticSearch
  8. VIVO's Docker container must be able to use SDB with the Dockerized MySQL
  9. Deployment of the VIVO components must be possible with a single command

Related tickets

  1. ...

  • No labels