Forum: Ruby on Rails Multi-Site sessions

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
40920c2420f2ed4841ff4ed2fc34c99f?d=identicon&s=25 Petr Janda (petrjanda)
on 2009-03-21 03:44
Hi all,
Im developing an application that runs on multiple physical boxes (and
thus different hostnames). Both of the boxes will run the same
application (connecting to a shared postgres server). What I need is
when someone logs in on box 1 (ie. box1.domain.com), and then traverses
via a link to box 2 (ie. box2.domain.com), he or she will not have to
login again.

How can I do this?

Thanks
Petr
81b61875e41eaa58887543635d556fca?d=identicon&s=25 Frederick Cheung (Guest)
on 2009-03-21 03:54
(Received via mailing list)
On Mar 21, 2:44 am, Petr Janda <rails-mailing-l...@andreas-s.net>
wrote:
> Hi all,
> Im developing an application that runs on multiple physical boxes (and
> thus different hostnames). Both of the boxes will run the same
> application (connecting to a shared postgres server). What I need is
> when someone logs in on box 1 (ie. box1.domain.com), and then traverses
> via a link to box 2 (ie. box2.domain.com), he or she will not have to
> login again.

That's what the :session_domain key for the session options is for.
Maybe there's more to your setup that you haven't described but if it
is exactly the same code running on the various boxes and you just
happen to have multiple ones because 1 couldn't service your load then
you don't need this at all. You can stick a load balancer in front,
users always go to www.domain.com and the load balancer spreads the
requests out to your various machines (the load balancer can be
anything from specialised hardware to software like haproxy, nginx or
apache).

Fred
40920c2420f2ed4841ff4ed2fc34c99f?d=identicon&s=25 Petr Janda (petrjanda)
on 2009-03-21 07:28
No its not because one box cannot handle the load, but because certain
activities the users would be doing are best done on a separate
high-performance box(other than the normal web-server).
40920c2420f2ed4841ff4ed2fc34c99f?d=identicon&s=25 Petr Janda (petrjanda)
on 2009-03-21 07:42
Anyway, session_domain works as expected. Thanks!

Petr
This topic is locked and can not be replied to.