Back
Use public-facing domain without generating certificates.
Hi, In my current setup I'm using Nginx which acts as a reverse proxy and is connected to LEGO which issues specific certificate (For appwrite and functions wildcard).
I'm worried that if I set mydomain.com instead of localhost the appwrite will try to generate certificate, which will be redundant. Is there any way to control this behavior?
Best thing (I think) would be to disable all HTTPS handling and leave only plain HTTP since TLS termination is handled at Nginx anyways.
My current workaround is to leave _APP_DOMAIN be localhost and change _APP_DOMAIN_FUNCTIONS to functions.mydomain.com
TL;DR
Developers are looking for a way to use a public-facing domain without generating certificates. They currently have Nginx as a reverse proxy connected to LEGO, which issues specific certificates. They are concerned about Appwrite trying to generate a redundant certificate if they set their domain instead of localhost. They would like to disable HTTPS handling and only use plain HTTP since TLS termination is handled by Nginx. Their workaround is to use localhost for `_APP_DOMAIN` and change `_APP_DOMAIN_FUNCTIONS` to functions.mydomain.com. 