@Philipp Kayser This file is being generated from a Jinja2 template, which can be found at /opt/atlassian/etc/seraph-config.xml.j2 inside the container. If you want to replace the template with your own template (this can contain merge fields, or can be a "normal" static file you've hand-crafted), simply overwrite the template file.
For example, to build from our image with your custom file:
FROM atlassian/confluence-server:latest
COPY seraph-config.xml /opt/atlassian/etc/seraph-config.xml.j2
You can also edit the "live" version of the template inside a running container, or copy your own file into a running container also. In other words, if you want to change it, change the template by whichever method you find most appropriate.
Having said that: Can you advise what changes you want to make to seraph-config.xml (I can guess, but I would like to make 100% sure).
One of our aims with our Docker images is to allow the maximum amount of from-the-environment configuration, since containers should be able to be "disposable" and configuration should always be able to be injected. If I can confirm your use case we can take a look at ways we can enable injecting the configuration you're after via a supported environment variable, which would allow you to avoid editing the file altogether
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.