tag:blogger.com,1999:blog-10678074.post7227223801907459029..comments2024-03-19T07:18:53.241+00:00Comments on making apps, making webs.: My fling with engine X.Unknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-10678074.post-77552383873751529642010-02-18T06:24:05.617+00:002010-02-18T06:24:05.617+00:00hey,
that sounds good. So far doing that with ju...hey,<br /><br />that sounds good. So far doing that with just a couple of sites that has given my server more resources.<br /><br />Using proxies seems fairly easy... like so:<br /><br />location ~ \.php$ {<br />proxy_pass http://apache_url/;<br />}<br /><br />For this one server it's about reducing memory usage... so to get better savings I'll have to stop using apache entirely. Probably not worth the effort for that reason alone... but maybe worth it to learn more about nginx.<br /><br />cya,René Dudfieldhttps://www.blogger.com/profile/17762358075557755436noreply@blogger.comtag:blogger.com,1999:blog-10678074.post-72467588572021256682010-02-17T17:15:15.479+00:002010-02-17T17:15:15.479+00:00Have you tried using Nginx in front of Apache as a...Have you tried using Nginx in front of Apache as a proxy? You configure nginx to serve the css, images etc., but you still hand over to Apache to run the dynamic parts and take care of the associated rewrites. That way you benefit of nginx's speed without bothering with fastcgi and translating every mod_rewrite rule.Anonymousnoreply@blogger.com