nextcloud
nginx containerPort confusion
Hello,
I'm trying to setup nextcloud with root-less nginx. So the default nginx port 80 won't work.
Thus I've set nextcloud.nginx.containerPort to 8080. This results in probe failures, because the nginx probes still refer to port 80.
Having a look at the chart templates, I notice that nextcloud.nginx.containerPort is only used for the nginx config, but not when settings up the container in the deployment. The nginx container make use of nextcloud.nextcloud.containerPort instead. I would consider this to be a bug.
On the other hand, when enabling nginx, nextcloud.nextcloud.containerPort is used only for the nginx container, not at all for the nextcloud container. So the simple workaround is to set nextcloud.nginx.containerPort and nextcloud.nextcloud.containerPort simultaneaously.
Still, I find this confusing. I would either join both variables into one or keep them completely separate -- i.e. the nginx container only uses nextcloud.nginx.containerPort, never the nextcloud.nextcloud.containerPort.
Regards, Carsten
It would be very helpful if guest accounts can see and add appointments.
Tested with 31.0.6 RC1 and guest accounts do receive the calendar invite.
Could you try again? I'm not aware of a specific change, but perhaps this was a bug in the past or someone enabled invites for guests in the meantime.
https://github.com/nextcloud/server/issues/26668 was added recently. This could be relevant if the old event was added to a shared calendar.