Skip to content

Setup local development environment for Dataverse backend #65

@GPortas

Description

@GPortas

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?

  • Frontend developers

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?

Metadata

Metadata

Assignees

Labels

MVP Milestone 2MVP Milestone 2: Add a DatasetSize: 30A percentage of a sprint. 21 hours. (formerly size:33)pm.GREI-d-2.7.1NIH, yr2, aim7, task1: R&D UI modules for creating datasets and supporting publishing workflowspm.GREI-d-2.7.2NIH, yr2, aim7, task2: Implement UI modules for creating datasets and publishing workflows

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions