That could well be part of it, but I'm afraid I'm not sure I follow you.
How would I go about doing that?
(I didn't need to with my old approach.)
Cheers,
Doug.
--
Posted via http://www.ruby-forum.com/.
--~--~-~--~~~---~--~~
You received this message because
On May 13, 7:56 pm, Doug Livesey rails-mailing-l...@andreas-s.net
wrote:
That could well be part of it, but I'm afraid I'm not sure I follow you.
How would I go about doing that?
(I didn't need to with my old approach.)
Ah, we may not be talking about the same thing. Are these apps on
On May 13, 8:56 pm, Doug Livesey rails-mailing-l...@andreas-s.net
wrote:
They're on the same machine, although I may want to move them at some
point.
that doesn't quite answer the question - even though they are on the
same machine any of the 3 scenarios I mentioned could be in effect.
What
I had something very similar on one of my applications with 2.3.2 the
action_controller.session has changed and its now just :domain
and :key :
config.action_controller.session = {
:domain = '.me.com',
:key = '_my_session',
:secret = 'long string'
}
This shares the me.com cookie with
Ah, I see, sorry -- well, they'll be on the same machine, but that is on
a local network (these are internal apps), and they are accessed by
names like app1, app2, with the local server's DNS resolving them to
the server address, and passenger and phusion taking over from there.
That's the
So if I have (locally) my apps all called things like app1.local and
app2.local, then I could set the domain to .local, which would
generate a local cookie that would be available to both apps, enabling
them to share a session?
Sorry if I'm labouring the point -- I've had my head in this all
6 matches
Mail list logo
