Setup local development environment for Dataverse backend

[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?

• Add Login / Logout mechanism #53

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?

• Dataverse container-based development environment dataverse#9423

[pdurbin]

We could use the "sample data" repo to create some datasets within the test environment: https://github.com/IQSS/dataverse-sample-data

Once upon a time @poikilotherm even worked a bit on Dockerizing it:

• WIP - 13 dockerize dataverse-sample-data#14

[poikilotherm]

Let me add that IQSS/dataverse#9447 is no longer a draft. Hopefully this is useful for this issue.