I have a couple of other threads going but will move the conversation here. I am looking at various groupware solutions to see which will provide the most integrated solution and can integrate into our model; we have not installed egroupware as yet. We are running a ZFS-based environment with our own ACME SSL service and an SSO service leveraging smartcard based gpg logins or mTLS. The identity provider is OpenLDAP based and supports nearly all authentication connectors. For containers we use podman.
Thanks to @RalfBecker, I now see that moving the database post-installation should be pretty straightforward. Simlarly I think exporting/importing the core and push-server docker images to podman should be no problem.
This leaves the remaining hurdle of the reverse proxy which we need to convert to using our PKI and should be handled by the host’s native apache service. Is there any way to configure this as part of the install process or is dockerized letsencrypt/certbot nginx revers-proxy the only option?
In general I don’t mind manually dis-assembling the installer to roll-my-own process for the initial install, nearly everything in our environment is custom; but I am concerned about how to prevent updates clobbering our customizations so I am trying to best understand what is where before proceeding.
Once the install is complete, is there any reason there would be problems with upgrading by pulling new docker images for just core egroupware and the push-server?
