2 ms·
Congrats on the launch! Is there any reason you're running an outdated version of Nginx (0.7.65 vs 0.7.68 vs 0.8.54)? It's one major revision behind current an
by jjoe 16y ago
Congrats on the launch!
Is there any reason you're running an outdated version of Nginx (0.7.65 vs 0.7.68 vs 0.8.54)? It's one major revision behind current and a few minor behind stable. Which brings me to a question I had lingering in my mind, what is your "software" upgrade process since users have no control over it?
Another question, do you cache non-static objects (cookie based caching when proxy_pass'ing)? If so, how are you handling the different cookies for each particular app? Can this be turned off?
Regards
Joe
- spahl 16y agoAbout the nginx version: - 0.7.65 is the version currently used in ubuntu lucid. We use it only as a proxy. - On services like python-wsgi we currently use 0.8.52 and we will soon upgrade to 0.8.54 - On the ruby-passenger service we follow the nginx pulled by passenger So it's always dependent of the context. The idea is to keep the stacks stable and secure at all times. Once we have tested and approved an upgrade we create a new revision of the corresponding service and deploy it across the platform. If the upgrade requires downtime we schedule a rolling maintenance window and notify users. On caching: We don't cache by default (but this could change). Users have the option to add caching services like varnish.