Allow for configuring alternative ports without reverse proxying

[LillyWho]

Describe your feature

I'm already running a web server on the same server which I wanted to use to host Stoat, but the guide only as a side effect of saying yes to reverse proxying runs the server on 8880. I don't need a reverse proxy, but I would like to simply tell the setup script to set caddy up for 8443 and 8080.

I was able to open port 8880 in my firewall and access the login page via http, but port 443 remains in use by apache and all my attempts at making Docker remap the container's port 443 have been met with the desired port still being unreachable, despite iptables being set to accept traffic on it.

[Dadadah]

The situation you're describing is exactly what reverse proxies are for. Consider setting one up.

That aside, you can edit the compose.override.yaml file to also forward 8443 to 443, but you will not be able to get a valid cert doing that. We will not be officially support this, so it will not be added to the generate-config.sh file

[LillyWho]

At least on the valid cert, it would be good to have support for pre-existing certificates. I've already got a let's encrypt certificate for my domain, so being able to reuse it would be so much easier.

I would still argue for being able to change ports. I shouldn't need an extra application, just to get the application to co-exist with others, when the application could simply internally allow for operating on whatever port the user specifies.

[Dadadah]

If you'd like to use a custom cert, you will need to read caddy documentation for doing so.

[LillyWho]

I still see no reason why the setup script shouldn't be able to ask for an existing certificate and reuse it, as well as ask for alternate ports without reverse proxying.