How to use a self-signed SSL certificate when developing with Trigger.io?
- by user610345
Our backend is in rails, and for several reasons the development environment has to be run with rails using a self-signed SSL certificate. This works fine on the desktop after manually trusting the certificate.
Using Trigger.io, we're developing a mobile application targeting iOS from the same backend. It would be ideal for us to be able to run the rails server with SSL (so we can compare the browser output) and still have the iOS simulator connect properly without complaining about invalid certs.
Production is using a proper ssl-cert, but what's the best way to set up the simulator?
