Does anyone have a preferred way of doing page/action caching across
multiple machines?   I know with fragment caching you can use
memcached.  But page caching usually goes in the document root, so it
is not usually in a shared directory.

I saw one suggestion which was to change the page cache directory to /
public/cache, and then modify the Apache re-write rules to check for
static content in /public first, and then /public/cache second.  But
that seems klunky.

Another crazy idea I heard was to possibly NFS/GFS mount the entire
application directory, and then your second application machine has
everything shared with the first one.  (Only PID file locations would
need to be kept separate.)

Does anyone have any experience or preferred methods on this?  There
is suprisingly little documentation on scaling Rails to multiple
boxes.

thanks,
Jeff

co-founder, cto
www.patientslikeme.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Deploying Rails" group.
To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to