Stream: containers

Topic: Default Docroot Location

Oliver Bertuch (Jan 08 2026 at 12:25):

To add files and stuff for branding, I need to put files into the docroot.

For a few things like sitemaps, logos etc we have setup "alternatedocroot_<n>" in glassfish-web.xml:

<property name="alternatedocroot_1" value="from=/guides/* dir=${MPCONFIG=dataverse.files.docroot:./docroot}"/>
  <property name="alternatedocroot_2" value="from=/dataexplore/* dir=${MPCONFIG=dataverse.files.docroot:./docroot}"/>
  <property name="alternatedocroot_3" value="from=/logos/* dir=${MPCONFIG=dataverse.files.docroot:./docroot}"/>
  <property name="alternatedocroot_4" value="from=/sitemap/* dir=${MPCONFIG=dataverse.files.docroot:./docroot}"/>

For the Logo Customization and other bits, I need to put files in either the default docroot (which is by default the domaindir/docroot folder) or one of the alternate docroots. As it's a bad practice to put files into the base image filesystem, I think I've got three options:

1. Mount a folder to the default docroot under /opt/payara/glassfish/server/domains/domain1/docroot
2. Add another alternate docroot for the branding and setup the all path to use it
3. Change the default docroot in the base image to make it configurable

Seeing that we already suggest people use /dv/docroot the put stuff for the alternate docroots, I'm leaning towards option 3, as it seems the cleanest. I'd like to hear more opinions!

Philip Durbin 🚀 (Jan 08 2026 at 15:13):

I'm not sure what the best option is but this all sounds highly related to this gotcha we document at https://guides.dataverse.org/en/6.9/installation/advanced.html#multiple-app-servers

• When users upload a logo or footer for their Dataverse collection using the “theme” feature described in the Dataverse Collection Management section of the User Guide, these logos are stored only on the app server the user happened to be on when uploading the logo. By default these logos and footers are written to the directory /usr/local/payara6/glassfish/domains/domain1/docroot/logos.

Oliver Bertuch (Jan 08 2026 at 15:20):

As all "logos" are already under an "alternatedocroot", we can have these on some other location already. So yes, related, but not part of the problem. As long as you put these logos on a ReadWriteMany type of filesystem (NFS/SMB/...), you're good to go. As it is configurable, you don't have to mount it to a "logos" subfolder of the docroot.

Philip Durbin 🚀 (Jan 08 2026 at 15:24):

I put this on the agenda for the next ct call but do you want to do a quick zoom?

Oliver Bertuch (Jan 08 2026 at 15:24):

Agenda sounds good. Room sounds good, too :smiley:

Philip Durbin 🚀 (Jan 08 2026 at 15:29):

https://harvard.zoom.us/my/pdurbin?pwd=em1WNUZGbnY2YjhxNEdSbjJJMXNSUT09

Oliver Bertuch (Jan 08 2026 at 16:01):

Phil pointed out a very valid 4th option: use a static webserver and serve the file from there. Benefit: can be cached locally and also serve more stuff later (previewers, SPA, ...)

Last updated: Jan 09 2026 at 14:18 UTC