Stream: containers

Topic: ✔ PR #9424: dv container for dev

Philip Durbin 🚀 (Mar 09 2023 at 15:15):

@Oliver Bertuch I just left a comment here: https://github.com/IQSS/dataverse/pull/9424#issuecomment-1462187824

Happy to discuss! I'm so excited about this PR! :rocket:

Philip Durbin 🚀 (Mar 09 2023 at 19:26):

I'm also happy to help, of course! I just don't want to step on your toes!

Oliver Bertuch (Mar 09 2023 at 21:26):

I'm just now hacking on the mdbtool to read TSVs and create the Solr configset. This is a crucial part for this to ship Solr images with a ready to go config/schema

Philip Durbin 🚀 (Mar 09 2023 at 21:31):

Ok, so a dependency, basically. Thanks! If there's any work that can be done in parallel (merging from develop?), please let me know!

Philip Durbin 🚀 (Mar 10 2023 at 11:10):

I guess I was hoping that the next steps for that PR (or do we need a new one?) are:

• merge in develop
• move the script that calls setup-all into the container
• let people on Windows try it (or Mac or Linux, but should work already)

Does that make sense? A small chunk that might give a new audience (developers on Windows) a working Dataverse development environment. And fewer steps for devs on Mac and Linux (no script to run on the side at the end). More automation, basically.

Oliver Bertuch (Mar 10 2023 at 11:23):

Yes and no. Yes to merge develop, but also requires adaption to move things from one file to the other. No to moving the script to the application image. Probably this part will become it's own container so it can be used for bootstrapping and potentially more.

Philip Durbin 🚀 (Mar 10 2023 at 11:39):

Sounds fine. No objection to running setup scripts in a separate container.

Philip Durbin 🚀 (Mar 10 2023 at 11:40):

When I look at the PR I see a long checklist and I had a much smaller scope in mind when I first pushed the branch. Maybe we could talk about scope? What to do in the PR vs future PRs?

Philip Durbin 🚀 (Mar 10 2023 at 11:50):

Something like this maybe:

• This PR: Merge from develop, get down to a single docker-compose script, send to QA
• Next PR: Move the setup script into a container
• Next, next PR: start building and pushing images for Dataverse to the GitHub image registry

At that point, the docker-compose becomes useful to a frontend dev who doesn't have Java installed. They pull the Dataverse image (for dev only!) from the GitHub image registry.

Does that make sense?

Oliver Bertuch (Mar 10 2023 at 13:21):

Sure! That PR description is rather fluid and was more a braindump of what's still left to do. Wrote this before the working group paper thingies were started, so we could transfer some of the text over there maybe for inspiration / base.

Philip Durbin 🚀 (Mar 10 2023 at 13:22):

Awesome. Would you like to do a quick call?

Philip Durbin 🚀 (Mar 10 2023 at 13:23):

(In theory, you can even do video calls in Zulip.)

Philip Durbin 🚀 (Mar 10 2023 at 13:26):

And yes, I need to wrangle the various docs into something readable. :sweat_smile:

Philip Durbin 🚀 (Mar 10 2023 at 18:06):

@Guillermo Portas and I talked and are planning the following:

• create a new issue
• start with PR #9424, make a new branch, merge in the latest from develop
• keep the "dev" docker-compose, remove the other
• remove mailhog :piglet:
• think about a better name for dev-rebuild-docker.sh
• docs, docs, docs

Philip Durbin 🚀 (Mar 10 2023 at 19:03):

Here's the issue we created: https://github.com/IQSS/dataverse/issues/9434

Philip Durbin 🚀 (Mar 13 2023 at 16:22):

@Oliver Bertuch just created a PR to close that new issue: https://github.com/IQSS/dataverse/pull/9439

And I just closed the old PR. Time to mark this topic as resolved. Thanks, all!

Notification Bot (Mar 13 2023 at 16:22):

Philip Durbin has marked this topic as resolved.

Last updated: Oct 30 2025 at 05:14 UTC