Back
Need Guide about the selfSigned in Appwrite
As for now, I hosted my appwrite in digital ocean. Because I am waiting for 1.3 version of appwrite cloud. Now I need your support.
- Am I right, if I am in dev mode is that it is necessary to selfSigned my appwrite client even tough I already hosted my appwrite in digital ocean.
- If the answer of number 1 is yes, then how can I avoid using selfSigned if I am in release mode.
TL;DR
User is seeking guidance on whether they need to use self-signed certificates in Appwrite if it is hosted on Digital Ocean. They reference the documentation but still need further support.
TL;DR:
- If your site has a valid SSL certificate, there is no need to use `setSelfSigned`.
- However, if you are running Appwrite locally (`localhost`), where a trusted SSL certificate might not be available, then you should use `setSelfSigned`.
- If you are hosting Appwrite on Digital Ocean, you may not need to use self-signed certificates.
- To avoid using self-signed certificates in release mode, make sure your site I read the documentation but I need your further support
If your site has a valid ssl certificate, no need to use setSelfSigned but if you are running appwrite locally (localhost) where a browser trusted ssl certificate may not be available then you should use setSelfSigned.
See SSL Certificates in Development section @ https://dev.to/appwrite/30daysofappwrite-ssl-certificates-c08.
@darShan so if my appwrite hosted in digital ocean do I still need to call the selfAssigned?
