So the patch panel will end up connected through at the front instead of being flush with the wall? And the wires would just be run out of the wall through to the front of the panel?
The cables would come out of your wall, go into the back of the network cabinet and would then be clicked into the patchpanel from behind. From the front of the cabinet you will just see RJ45 ports that you then can connect to your switch. The back of the patchpanel will look something like this.
Out of interest, what’s the alternative? Is it that the cables would be hard wired directly into a particular port of the patch panel and not be movable?
Exactly. The patchpanel would provide a board where you could patch your cables into (like this).
Another thing I would recommend is having a “service loop”. That means leaving a bit of extra cable when exiting the wall in case you need it. Otherwise you might need to pull a whole new cable if something unforseen happens and that sucks.
Not OP but I’m doing almost the same thing in Kubernetes. Basically you start a Nextcloud container but only to run the cronjob, not Nextcloud itself. In my case, Kubernetes creates a new container for each cron execution. Apparently there’s also a cron.sh script already bundled with the Nextcloud image, that can run continously. At least OP doesn’t seem to mount the script from somewhere else.