WordPress image doesn't do HTTPS with a public IP

[scottyeager]

When the WordPress image is deployed, it doesn't attempt on its own to obtain an TLS certificate or serve traffic over HTTPS. That's okay when a TLS terminating gateway is used in front of the deploymen. However when the user reserves a public IP for the VM, they will be left with HTTP only service for WordPress.

Ideally the image can dynamically provide its own TLS termination if needed, based on environment variables passed at time of deployment. In the case that the VM needs to provide TLS, adding Caddy as a reverse proxy in front of Apache is a simple way to do this reliably.

We used a similar approach in the NextCloud image that could be of interest as a reference.