<p>This is more than likely a newbie question, but I don’t see it covered anywhere.</p>
<p>The scenario is:</p>
<p>I have two sites, one for back-end editing, one for front-end viewing. These are two separate Rails projects that share a single database. A team of reporters enters content into the back-end that shows up in the front-end.</p>
<p>The back-end uses acts-as-authenticated. The front-end does not (because it’s public).</p>
<p>The problem is, when the reporter (or anyone) logs into the back-end, and then goes to look at the front-end, the front-end clears the session, and now they have to log back into the back-end.</p>
<p>Is there a way to avoid this?</p>
<p>Thanks in advance!</p>
<p>—————</p>
<p>Then make the front-end stop clearing the session. Simple really. Maybe you’re having issues with your session? Also, separate apps use separate session keys I believe. If not, they may be clobbering each other.</p>
<p>The SessionManagement module shows how to modify the session. Use the session class method in your controllers to modify session properties for a group of actions, or config.session_options in environment.rb to change the default options.</p>
<p>ActionController::Base.process_cgi lists the possible session options.</p>
<p>This wiki probably isn’t the best place to ask questions. Try Rails Weenie.</p>
<p>—————</p>
<p>The problem you are having is two cookies that creates two sessions. Let say you ahve two sites with these two URLs: admin.domain.com and www.domain.com. For such a situation what you need to do is setup your session to use the domain ”.domain.com”. Then your browser will create only one cookie for both domains and you will end up with only one session.</p>
<p>Hope it helps,</p>
<p>Adrian Madrid<br />
————————</p>
<p>Check out:</p>
1. class ApplicationController < ActionController::Base
2. # …
3.
4. <span class="caps">DOMAINS</span> = [‘example.com’, ‘example.net’].freeze
5.
6. <span class="caps">DOMAINS</span>.each do |domain|
7. session :session_domain => “.#{domain}”, :if => lambda { |request| request.host.dup.chomp!(domain) }
8. end
9.
10. # …
11. end
<p>http://www.railsweenie.com/forums/1/topics/597</p>
2008-10-24T03:35:57-07:00
71685
using-with-multiple-sites
67186
Using with Multiple Sites
2008-10-24T03:36:44-07:00
30799