And we didn't even fulfill all of milestone A yet :see_no_evil: Anyone up for docs writing?
@Oliver Bertuch if you start the branch and (eventually) make the pull request, I'll contribute to it!
Here's a handy link to the issue: https://github.com/IQSS/dataverse/issues/9540
Maybe you could explain how to view logs? That's probably one of the easier bullets.
D'oh! I thought I wouldn't need to write docs :grimacing:
Here's a diff to get you started:
$ git diff
diff --git a/doc/sphinx-guides/source/container/dev-usage.rst b/doc/sphinx-guides/source/container/dev-usage.rst
index 4eba70eb23..4a12902c06 100644
--- a/doc/sphinx-guides/source/container/dev-usage.rst
+++ b/doc/sphinx-guides/source/container/dev-usage.rst
@@ -49,3 +49,7 @@ You can also access the Payara Admin Console if needed, which is available at ht
Note that data is persisted in ``./docker-dev-volumes`` in the root of the Git repo. For a clean start, you should
remove this directory before running the ``mvn`` commands above.
+
+To view the Payara server.log file:
+
+``docker logs dataverse-1``
You could just call the branch 9540-docs.
In the main repo, please.
Then I'm happy to add more commits.
Oh, we don't need a single PR to fix all the docs stuff at once. We can merge as we go. Instead of "closes" we can say "related to".
Here's a thought: how about we add more docs about containers to the container guide, remove the "Docker, Kubernetes and Containers" page from the Dev guide and create a new Dev Guide page on "Continuous Integration", that can hold all of our stuff we do with GH actions now and in the future? (So we move and update the CI part in http://preview.guides.gdcc.io/en/develop/developers/testing.html#continuous-integration into it, which is grossly outdated, mentioning Phoenix et al)
A new page in the dev guide on CI where we can talk about GitHub Actions sounds good.
I don't feel strongly about removing the old containers page. It serves a useful purpose of directing people to the new Container Guide.
Question @Philip Durbin: in milestone A we say "explain how to redeploy"
Would it help to explain how to run the containers in background?
Maybe also explain how to just run the app container in foreground?
Or restart just this one when it's in background?
I feel it's getting more and more containers and all of those take obviously time to start
Yes, I think @Jan Range requested that -d be documented.
That's compose syntax
Do we want compose syntax?
For the redeploy you need Maven anyway
(Recompile, rebuild, ...)
Yes, like the issue says, we want to write about vanilla docker compose syntax.
Looks like I need to read the issue :-D
I was reading our milestone again :-D
The issue is living. :happy:
Yeah...
Hard part: if you start via compose you won't be able to replace the app container via mvn
OK that's not completely true - you can of course make it two commands, then that will work as well
I'm definitely interested in trying that "watch" thing you added. I forget if I told you but I'm slowly working on using the Maven Docker Plugin for the people app. Maybe we can play with watch there: https://github.com/IQSS/dataverse-people/compare/docker-build-scratch
Right now for both "people" and Dataverse, I just redeploy the dumb way.
That is not the "hard way" :smile:
But yeah, I'd be interested in trying out watch
I'm not sure this is going to work out because the Dockerfile has the knowledge about where to place the files. So maybe "copy" mode won't work.
But I do have an idea involving mounting the exploded dir into the container. Try hot reload from the container
And of course there is JRebel :smile:
Lots of ways to improve over what I'm doing now. :sweat_smile:
Question: I'm writing up the different ways of running this
Do we want some ascii cinema examples?
So people get an idea of what things look like?
http://hhoegl.informatik.hs-augsburg.de/es2/sphinx-asciinema/_build/html/main.html
I'd probably wait on that, especially if it adds a Sphinx dependency.
https://github.com/IQSS/dataverse/pull/9584
Thanks! I'm on the branch poking around!
In the backlog I replaced the issue with the PR.
Where should we drop the notes about running SMTP only? Sound like Dev Guide to me...
Here's the preview BTW https://dataverse-guide--9584.org.readthedocs.build/en/9584/container/dev-usage.html
We should probably edit this:
The installer will try to connect to the SMTP server you tell it to use. If you havenβt used the Docker Compose option for setting up the dependencies, or you donβt have a mail server handy, you can run nc -l 25 in another terminal and choose βlocalhostβ (the default) to get past this check.
Over at https://dataverse-guide--9584.org.readthedocs.build/en/9584/developers/dev-environment.html
Sounds good to me
Lemme know what you think about the tables.
They look good but we might want a quickstart at the top.
An opinionated quickstart. Just do this.
And then show the tables below.
Ok I'll add a tl;dr in the intro
Should we mention that the build step isn't necessary if you pull from Docker Hub or GHCR?
No I wouldn't do that
This guide is targeted towards people doing Java dev work
For the occasional drop-by we might write some other guide
And probably want some other compose file
Let's tune this heavily towards a "real dev"
And for integrators we definitely need a different page
Ok. This is coming: https://github.com/IQSS/dataverse-frontend/blob/eaf26512eb414f79cbefc0fe4389ce478016f59c/README.md#local-development-environment
Which mentions containers. We can link to it.
@Philip Durbin what was that all about?
Update Windows dev page: https://guides.dataverse.org/en/5.13/developers/windows.html A cloned Dataverse by Git for Windows with the line-ending setting is set to always LF (core.autocrlf=input)
You can leave that Windows page to me.
You might have seen I turned https://github.com/IQSS/dataverse/issues/9540 into a checklist...
I hadn't but looks great, thanks.
Do you want to document the SMTP part as well? You played around a little with it...
Yes, I'm happy to.
You've written a ton of docs! Thank you! A stub would have been enough! Much appreciated!
I'm even looking into writing about redeployment aside from stopping 'em all and starting 'em all again
Moved the discussion about redeployment options to #containers > faster redeploy
@Philip Durbin what do we do with https://github.com/IQSS/dataverse/pull/9584 ?
(I merged develop and solved the conflict)
I guess I'm thinking...
Hmm can we get on the fast lane with this docs only PR? It's just our (=container) docs...
There's a good chance, yes.
I updated the docs with the latest changes from develop (configbaker image), solving the merge conflicts
Here's the preview of the dev usage page: https://dataverse-guide--9584.org.readthedocs.build/en/9584/container/dev-usage.html
Looks good but I may turn that tl;dr into a quickstart
Thanks for resolving the merge conflicts!
I'd rather have the quickstart after the intro, as it lists the prerequisites (Docker, Java, Maven)
In the frontend README only Docker is required. Even quicker! :happy:
Yeah well suppose they don't need to wrestle with all sorts of stuff being moved around...
@Philip Durbin what are we gonna do with https://github.com/IQSS/dataverse/pull/9584 now after DCM and probably close to 5.14?
I should get on that branch and hack a bit.
Ha! That's true!
I should probably go ahead and hack on mail stuff to solve Milestone C
During the demo, you showed the preview of that PR, right?
Nope. That was about MPCONFIG for OIDC
Oh. Well, I guess the docs in develop were good enough then :sweat_smile:
for demo purposes
Dunno if that is going to make it into 5.14 or 6.1 :smile:
Yes, exactly - show the integration with Keycloakl
It would be nice to have that in 5.14 but I suppose you folks don't want more on your plates
Check out https://github.com/IQSS/dataverse/pull/9584#issuecomment-1596320823
https://github.com/IQSS/dataverse/pull/9584 was merged as part of 5.14, now released. Good job, all.
Philip Durbin has marked this topic as resolved.
Last updated: Oct 30 2025 at 05:14 UTC