hook scrtipts for before/after applying configuration changes?

While I think you are going down the wrong road (using nginx for other sites?), it depends on the version of OMV. On OMV 4.x, you could add a higher numbered mkconf to run after the other config scripts. On OMV 5.x, you might be able to add saltstack code to do this.

Zitat von mortee

yes, I think it's a bit overkill to run a whole separate nginx in a docker to make other sites available, when there's already a perfectly fine nginx already running and serving OMV itself.

I disagree. Most web sites are served to the internet. Having your OMV web server needlessly available to the internet is bad. nginx is very lightweight and having multiple instances running on the systems mean very little. docker gives a little extra security and if an update to OMV or nginx breaks the nginx config, having sites in docker won't be broken.

Zitat von mortee

if OMV wouldn't add a listen [::]:443 line to the server block

It is only supposed to do this IF ipv6 is determined to be enabled.

https://github.com/openmediava…/files/site-webgui.j2#L48

https://github.com/openmediava…/files/site-webgui.j2#L60

Zitat von mortee

Any advice on how I could work this around without actually disabling said line in the generated file?

Disable ipv6

Zitat von mortee

where can I find pointers to the "saltstack" thing?

Here is the code - https://github.com/openmediava…vault/srv/salt/omv/deploy

Zitat von mortee

I don't find any setting regarding this on the UI.

Set the value of net.ipv6.conf.lo.disable_ipv6 to 1 in /etc/sysctl.d/99-openmediavault.conf and reboot

Then omv-salt deploy run nginx