Date: Thu, 28 Mar 2024 14:28:09 -0400 (EDT)
Message-ID: <1122988916.28596.1711650489967@lyrasis1-roc-mp1>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_28595_1275822077.1711650489967"
------=_Part_28595_1275822077.1711650489967
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Design - Dockerizing VIVO
Design - Dockerizing VIVO
As a step towards modularizing and streamlining the deployment o=
f the VIVO application, an initial set of components have been identified a=
s 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 t=
he deployment of the components above.
Requirements
- Core VIVO must be deployable as a Docker container
- VIVO's configu=
ration files must be configurable at deploy-time (runtime.properties, applicationSetup=
.n3)
- VIVO's Solr must be deployable as a Docker container
- VIVO's ElasticSearch must be deployable as a Docker container
- VIVO's MySQL must be deployable as a Docker container
- VIVO's Docker container must be able to use the Dockerized Solr
- VIVO's Docker container must be able to use the Dockerized ElasticSearc=
h
- VIVO's Docker container must be able to use SDB with the Dockerized MyS=
QL
- Deployment of the VIVO components must be possible with a single comman=
d
- ...
------=_Part_28595_1275822077.1711650489967--