Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Containerize Dataverse service dependencies for development #9414

Closed
GPortas opened this issue Mar 1, 2023 · 0 comments · Fixed by #9417
Closed

Containerize Dataverse service dependencies for development #9414

GPortas opened this issue Mar 1, 2023 · 0 comments · Fixed by #9417
Assignees
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

Comments

@GPortas
Copy link
Contributor

GPortas commented Mar 1, 2023

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?

@GPortas GPortas added NIH OTA: 1.7.1 (reArchitecture) 7 | 1.7.1 | Research & architecture for separating backend and frontend to enable a flexible, sca... Size: 30 A percentage of a sprint. 21 hours. (formerly size:33) labels Mar 1, 2023
@GPortas GPortas added Component: Code Infrastructure formerly "Feature: Code Infrastructure" Feature: Developer Guide Component: Containers Anything related to cloudy Dataverse, shipped in containers. labels Mar 1, 2023
@GPortas GPortas changed the title Containerize Dataverse service dependencies Containerize Dataverse service dependencies for development Mar 1, 2023
@GPortas GPortas self-assigned this Mar 1, 2023
GPortas added a commit to GPortas/dataverse that referenced this issue Mar 3, 2023
GPortas added a commit to GPortas/dataverse that referenced this issue Mar 3, 2023
@mreekie mreekie added the pm.GREI-d-1.7.1 NIH, yr1, aim7, task1: Research & architecture for separating backend and frontend label Mar 20, 2023
@pdurbin pdurbin added this to the 5.14 milestone May 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants