Lighttpd to serve /var ?

Monday 11 February 2008 12:27:03 am

Is there an option to set up the var-directory serving from a different source? I would be interested in serving static content from the /var -directory via lighttpd and everything else through Apache.

It's a no-brainer to set up lighttpd to serve /var in virtual host (say static.example.com), but how do I get eZ Publish to write the references to static.example.com instead of www.example.com?

In the RAILS-community people have done some stuff using Apache proxy features. http://www.howtoforge.com/reduce-apache-load-with-lighttpd-debian-etch I'm sure I could get it to work, but it seems... well. hackish.

And I'd prefer a real virtual host to circumvent the two connections per host limit (http://ajaxian.com/archives/using-cnames-to-get-around-browser-connection-limits). Sure it'd be even sweeter to have multiple static servers, say static1.example.com, static2.examp... and so forth. But that'd go over the top and it'd be easy to have issues with client-side caching if the domains for a resource change over time.

--
http://ezpublish.fi/

Monday 11 February 2008 1:50:22 am

Thanks for your reply. I was just wondering whether there's an out-of-the-box -setting for this. I'll have a closer look as we're far enough that this would be relevant :)

As for the domain to host static content... I think it might make sense to prepend static to the domain at hand. For example the static url for www.example.com could just aswell be static.www.example.com.

Another thing... Does anyone have any benchmark on using Apache's mod_mem_cache ( http://httpd.apache.org/docs/2.0/mod/mod_mem_cache.html )? Apparently it's still experimental, but is included with Debian Etch Apache2 package.

--
http://ezpublish.fi/

Monday 11 February 2008 5:11:44 am

Hi,

I have done this setup on a high traffic site with rewrite, but it did not work as expected.

Apache will always use more resources for all requests if mod_php is enabled.

Another possible solution is to use a proxy or some kind of load-balancing in front of Apache. Lighttpd, squid or varnish is one of the possibilities.

Try out Free eZ Publish 4.0 Trial Hosting for 14 days:
http://webdealhosting.com/ez-publish-trial-hosting

High quality eZ Publish Hosting since 2001!

Monday 11 February 2008 5:40:15 am

Thanks Kim,

> Apache will always use more resources for all requests if mod_php is enabled.

Exactly what I thought. Proxying lighttpd through Apache with mod_php seems pointless.

> Another possible solution is to use a proxy or some kind of load-balancing in front of Apache. Lighttpd, squid or varnish is one of the possibilities.

Yeah, I thought about using Squid IF we'll need to enable clustering. I know that'd ease the load on the 'ol database when we're fetching images, etc. from there.

But as of now, it looks like I'll just run everything through Apache to avoid extra components. I'll probably look into mod_mem_cache, etc.

--
Jani

--
http://ezpublish.fi/

Tuesday 18 March 2008 4:57:53 am

http://ez.no/developer/open_funding/suggestions_for_new_functionality/http_acceleration_with_varnish

Mit freundlichen Grüßen
Best regards

Norman Leutner

____________________________________________________________
eZ Publish Platinum Partner - http://www.all2e.com
http://ez.no/partners/worldwide_partners/all2e_gmbh