Document competing containerization efforts and how to choose
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
As @johannes-darms has pointed out, it can be confusing for a newcomer who stumbles upon a variety of containerization efforts for Dataverse:
- https://github.com/IQSS/dataverse/blob/develop/docker-compose-dev.yml
- https://github.com/IQSS/dataverse/blob/develop/docker/compose/demo/compose.yml
- https://github.com/IQSS/dataverse-docker
- https://github.com/gdcc/dataverse-kubernetes
- https://github.com/EOSC-synergy/dataverse-kubernetes
- https://github.com/link89/dataverse-docker
Which one should they choose?
Let's clean up and reorganize the information we have at the following pages:
- https://guides.dataverse.org/en/6.2/developers/containers.html
- https://guides.dataverse.org/en/6.2/container/intro.html
We can also add more to the README at https://github.com/IQSS/dataverse/tree/develop/docker which relates to this issue:
- #10157
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the guidance in developers/containers.html, container/intro.html, and the docker README with the listed Docker Compose and Kubernetes efforts. Document how the options differ and which use case each supports, so a newcomer can choose confidently; check #10157 for related context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, kubernetes
- Domain
- devops, documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100