Containerize Dataverse service dependencies for development #9414
Labels
Component: Code Infrastructure
formerly "Feature: Code Infrastructure"
Component: Containers
Anything related to cloudy Dataverse, shipped in containers.
Feature: Developer Guide
NIH OTA: 1.7.1 (reArchitecture)
7 | 1.7.1 | Research & architecture for separating backend and frontend to enable a flexible, sca...
pm.GREI-d-1.7.1
NIH, yr1, aim7, task1: Research & architecture for separating backend and frontend
Size: 30
A percentage of a sprint. 21 hours. (formerly size:33)
Milestone
Overview of the Feature Request
This issue is created within the scope of #9423, and separated from it since the containerization of the Dataverse dependencies (Postgres, Solr and smtp server) is itself an enhancement to the development environment setup.
In this way, although we still need the install.py script for installing the Dataverse application, we offer a different and more automated way to install its dependencies (through Docker containers).
In addition to creating the necessary configurations to run the containers, it will be necessary to update the documentation related to the development environment setup to offer this alternative.
What kind of user is the feature intended for?
Developers
What inspired the request?
What existing behavior do you want changed?
Dataverse development environment setup
Any brand new behavior do you want to add to Dataverse?
No, should be the same.
Any related open or closed issues to this feature request?
The text was updated successfully, but these errors were encountered: