How to set up stress-free SSL on an OS X development machine
gist.github.com
How to set up stress-free SSL on an OS X development machine
1–10 of 23 posts
Re: How to set up stress-free SSL on an OS X development machine
#2I usually just use https://github.com/jugyo/tunnels.
Re: How to set up stress-free SSL on an OS X development machine
#3I didn't see self-signed certs as an alternative. Isn't that a common and reasonable approach?
Re: How to set up stress-free SSL on an OS X development machine
#4I didn't see self-signed certs as an alternative. Isn't that a common and reasonable approach?
This describes setting up a self-signed cert
Re: How to set up stress-free SSL on an OS X development machine
#5Keychain Access makes creating a certificate authority very easy - you might as well just use that...
Besides, I don't understand why you would choose not to trust the certificate, then click it and choose to trust it...
Re: How to set up stress-free SSL on an OS X development machine
#6I use ngrok (https://ngrok.com/), which tunnels a local port and makes it available over ssl on an ngrok.com subdomain.
Makes it easy to develop from any machine, and even allows me to check it out from other machines. Including things like browserling.
On top of that, it can record and replay requests for you as you debug.
Re: How to set up stress-free SSL on an OS X development machine
#7/etc/resolver is pretty cool. I wish it were better-documented / better-known. (I guess `man 5 resolver` documents it.)
I also wish glibc had something similar.
Re: How to set up stress-free SSL on an OS X development machine
#8Only gripe is being told to match Dev with production ... And then develop on Mac OS.
Virtual machines are a much cleaner and nicer way to do this. Setting up a wildcard SSL is similarly as simple, an you get the bonus of learning how to do it on a "real" (normal, more standard) server.
Example setting up wildcard subdomain SSL cert (self-signed): https://serversforhackers.com/ssl-certs/
Re: How to set up stress-free SSL on an OS X development machine
#9Only gripe is being told to match Dev with production ... And then develop on Mac OS. Virtual machines are a much cleaner and nicer way to do this. Setting up a wildcard SSL is similarly as simple, an you get the bonus of learning how to do it on a "real" (normal, more standard) server. Example setting up wildcard subdomain SSL cert (self-signed): https://serversforhackers.com/ssl-certs/
Having gotten more accustomed to the VM approach over the past year since I wrote this post, I agree.
Re: How to set up stress-free SSL on an OS X development machine
#10Instead of dnsmasq you can also use https://github.com/robbiev/devdns