Make TLS certificate configuration optional?

[Lx]

Thank you for your efforts. Would you consider producing a version of this without the TLS certificate configuration (or somehow making this optional)? I'm looking to deploy this behind an established reverse proxy (unless I'm oblivious to something that prevents this?) and the reverse proxy already manages all the TLS stuff, so it would be preferable in this instance for RT to serve over HTTP only.

[firefart]

Hi, you can completely change the nginx config via the startup scripts. Those are simple shell scripts that get executed before nginx loads so you can change anything in the config with them, you could even replace the whole nginx config with them.

But I would just serve it with a self signed certificate and let the proxy connection to this server be encypted too if that's possible.

[Lx]

Thanks for the rapid response. I hadn't considered using a self-signed certificate, but I suppose this wouldn't cause issues for the end user, because the end user wouldn't be seeing it. I'll give this a shot.