| 1 |
>>>>>> Changing completely from a user-facing apache to a user-facing nginx |
| 2 |
>>>>>> sounds fraught with peril. |
| 3 |
>>> |
| 4 |
>>> The last time I set this up was for one of our e-commerce sites on Centos. |
| 5 |
>>> |
| 6 |
>>> It went like this: |
| 7 |
>>> |
| 8 |
>>> install nginx |
| 9 |
>>> vi config file |
| 10 |
>>> change obvious stuff |
| 11 |
>>> tweak location of nginx and backend web server |
| 12 |
>>> restart stuff |
| 13 |
>>> stuff worked |
| 14 |
>>> |
| 15 |
>>> Even the SSL certs was mind-bogglingly easy. Copy it over to nginx. |
| 16 |
>>> Sorted. Done. |
| 17 |
|
| 18 |
You guys were so right. What an excellent http server/proxy. I used |
| 19 |
this very simple howto: |
| 20 |
|
| 21 |
http://kbeezie.com/apache-with-nginx/ |
| 22 |
|
| 23 |
I can probably dump a lot of apache config. I still need SSL on both |
| 24 |
servers even though only nginx faces the user? |
| 25 |
|
| 26 |
For imap proxy, nginx requires an HTTP auth server and I can't figure |
| 27 |
out what that refers to. I can stick with imapproxy there. |
| 28 |
|
| 29 |
- Grant |
Archives