On 07/03/2013 23:48, Grant wrote: >>> It sounds like having apache serve dynamic .html pages and nginx >>> serve images on the same port means turning apache into a proxy for >>> nginx which I'm hoping isn't too difficult. Could this pose any >>> problems for an ecommerce site? >> >>> Changing completely from a user-facing apache to a user-facing nginx >>> sounds fraught with peril. >> >> Yet this is the way it's done. If you have apache serve as a proxy for >> nginx, you gain absolutely *nothing*; every inbound connection still >> takes Apache resources, and that's exactly what you need to introduce a >> proxy to alleviate. > > Understood. Can anyone who has made a switch like this comment on > potential (SSL-related?) pitfalls?
The last time I set this up was for one of our e-commerce sites on Centos. It went like this: install nginx vi config file change obvious stuff tweak location of nginx and backend web server restart stuff stuff worked Even the SSL certs was mind-bogglingly easy. Copy it over to nginx. Sorted. Done. Lucky for me, I could firewall off the backend web server from the entire world so users never see it directly. This let me dispense with a CE signed cert for the backend and just create my own. -- Alan McKinnon alan.mckin...@gmail.com
