Setup local development environment for Dataverse backend #65
Labels
MVP Milestone 2
MVP Milestone 2: Add a Dataset
pm.GREI-d-2.7.1
NIH, yr2, aim7, task1: R&D UI modules for creating datasets and supporting publishing workflows
pm.GREI-d-2.7.2
NIH, yr2, aim7, task2: Implement UI modules for creating datasets and publishing workflows
Size: 30
A percentage of a sprint. 21 hours. (formerly size:33)
Overview of the Feature Request
The goal is to establish an automated mechanism to initialize a Dataverse instance, with all its dependencies, locally, for frontend development purposes.
It is important that the Dataverse instance is configured with the session authentication feature flag enabled to allow session cookie authentication.
We can build the solution from the current container-based development mechanism based on docker-compose, present in the core repository, and adapt it to the needs of the frontend.
EDIT: it will be necessary to create a proxy on top of SPA and Dataverse to avoid CORS issues.
What kind of user is the feature intended for?
What inspired the request?
What existing behavior do you want changed?
No
Any brand new behavior do you want to add to Dataverse?
Add a local dev environment for Dataverse
Any open or closed issues related to this feature request?
The text was updated successfully, but these errors were encountered: