dataverse:
container_name: "dataverse"
hostname: dataverse
build:
dockerfile: ./dataverse/Dockerfile
args:
- BASE_VERSION=${BASE_VERSION:-6.6-noble}
- DATAVERSE_WAR_URL=${DATAVERSE_WAR_URL:-https://github.com/IQSS/dataverse/releases/download/v6.6/dataverse-6.6.war}
- USER_ID=${USER_ID:-1000}
- GROUP_ID=${GROUP_ID:-1000}
From @Eryk Kulikowski at https://github.com/libis/rdm-integration/blob/bca3826674a426522fdd75437b0e4ff54234f6e6/docker-compose.yml#L66
What I like most in that repo: the modularized approach to setup. @Eryk Kulikowski this would be good to have in upstream, too!
Absolutely. That compose file was something we only touched on during tech hours but I'd love to hear more.
I just opened a PR that might be interesting for the upstream repo:ย https://github.com/IQSS/dataverse/pull/11961
It adds fast-redeploy scripts for container-based development that reduce iteration time from ~54s to ~12s (4.5x faster). The workflow uses exploded WAR deployment with incremental compilation and Payara's asadmin deploy --force for hot redeployment without container restarts.
Key features:
This could be a good topic for tech hours - we could discuss what developer workflow improvements would be valuable to include in the mainstream Dataverse repo.
@Eryk Kulikowski THANK YOU!
And yes, I'd love to hear from other developers any tips and tricks to speed up development!
@Eryk Kulikowski I really like what you did in your PR! Thanks for testing out all of this stuff and looking into making it work!
I have a few suggestions and maybe we should discuss them here in chat or during the next containerization meeting.
Braindump / Notes to self:
cargo.glassfish.deploy.arg.forceLast updated: Jan 09 2026 at 14:18 UTC