Wordpress template doesn't let you specify the port explicitly
The configuration in the template just uses a port definition of 80, which results in a randomly-assigned port when the container is started/restarted.
This makes it difficult to put Wordpress behind a reverse proxy, because the port is always changing. It would make more sense to allow the user to specify the port in the configuration, similar to how the DB password is defined.
@hendersj you can always copy the template as a custom one and override that configuration.
Oh, yes, making a copy is a way of handling it - I was thinking in terms of ease of use for everyone using it.
I edited my running instance to set the port statically, but it would be nice to be able to define it during startup.