You can use your existing production certificates for your local setup, and use a local DNS server (such as BIND) to resolve the domain name to your local ip address instead of your production servers ip address.
Update:
- Install BIND (or whatever DNS server software you like) on some computer on your network, let us say 192.168.100.10.
- Add www.myprodserver.com to resolve to 192.168.100.100.
- Now on your local machine (assume its a MacBook), go to your network settings and add 192.168.100.10 as the only DNS server.
- Now run ping www.myprodserver.com and make sure it is resolving to 192.168.100.100.
This is almost equivalent (but not exactly) to using /etc/hosts
file to resolve domain names to ip addresses .
(all ip addresses and domain names used above are just for example)
Also, I think you will need something better than WEBRick
to handle SSL certificates. You can use nginx
to offload SSL and proxy to WEBRick