On 3/21/07, Liam Hoekenga <[EMAIL PROTECTED]> wrote: > I know there are other session handlers, but I imagine that without > fixing the umask, we'd run into the same issue with any other file > created in the various subdirectories under "tmp" (cache, pids, sessions > and sockets).
The best way to handle this is to make your rails set up as "shared nothing" as possible. Each Rails app should be independent. Store your sessions in the database, and then use Apache 2.2's mod_proxy_balancer to route requests between Mongrel processes on the various boxes you have. The only place you need shared storage in this set up is for user uploaded files (and even then, you could go with something like S3). Hope this helps, Luke Francl --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
