Posts by mortee

    FWIW, 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 used to use the Services / Sites feature for this in 3.x, which does exactly that, and is perfectly suitable for this purpose. And actually, I wouldn't even need to touch any auto-generated files for this if OMV wouldn't add a listen [::]:443 line to the server block. Which, in this form, based on my experience, causes a conflict in nginx if any other service block has a similar line. So, I need to comment this out, just to be able to add a simple listen 443 line in there.


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


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

    Hi,


    Is there a way to hook into when configuration changes are applied through the UI? In particular, I would like to make changes to the automatically-generated nginx config files, and keep those changes across config modifications. So, I'd prefer a hook script which is called after everything is written, but before nginx is restarted.


    thanks

    The same would've been the outcome. I figured out what happened in the first place.


    The image has a /root/.rootfs_resize file (I think - posting this from memory), with a requested FS size slightly larger than the sd card is. But the resize2fs script does not check this, and tries to fdisk it anyway, which thus rejects to save the new partiton table, and everything stays unchanged. Which is sad, since this way the space which IS available after the root partition remains inaccessible.


    The quick fix was to specify a smaller size in that file and re-run the script; thus the partition got resized, and also a (small) third partition created, which is useful to me (I can define a shared folder which is available even when the external hdd is not).

    I'm trying to install OMV 3 on a Raspberry Pi using the image OMV_3_0_88_RaspberryPi_2_3_4.9.41.img.xz. As far as I know, it is suposed to resize the system partition on the first run, and create a third partition for the rest of the sd card. However, my system partition is only 2.6GB on a 8GB sd card, and I don't see a third partition at all.


    What may be the problem, and how do I go about re-running the script that does this trick? I did try to re-enable the firstrun and resize2fs services, tried to start them, restarted the system with these enabled - but still no success.