a bit curious how you do know I have a different approach, as I haven’t talked about it
I’m not sure about the use case of this added setting. Are you proposing that Caddy should listen to a port other than 443 like 8443 for https? I feel like this is useless, let’s encrypt only verify the domain at 80 and 443, so in this case, user will need to provide a cert for their domain. Then why don’t they offload TLS at the reverse proxy in the front?
Additionally, I’m thinking about adding a variable HTTPS_MODE, which can be off, manual and auto. The problem with current ENABLE_HTTPS variable is that if I want to use my own cert behind a reverse proxy, I have to set ENABLE_HTTPS to false as Caddy cannot bind port 443, and that would lead to LMS_ROOT_URL to be http, which should start with https.
By adding the three modes, users get to choose if s/he want to have Caddy auto-provisioned https, or manage https themselves.
I’m not sure about this. Currently Nginx isn’t doing logging right? Could you please elaborate more on this? Highly appreciate this!
Totally understand and fully agree.
link is dead but i suppose it’s Tutor Enhancement Proposals (TEPs) - Overhang.IO?