How about using a single Rails app and configuring your apache or webserver to point two domain names to the same application. Then, based on the domain in the login request, you can determine how to authenticate your user.
On your "User" model, would associate each user with a domain (ex. domain1 or domain2) which would govern business logic depending on the user. On Mar 27, 5:15 pm, Rike Hahn <[email protected]> wrote: > Hi, > > I just finishes my first RoR application and I'm happy that nearly every > problem I had was solved. But now I need your help. The problem is that > an other organisation wants to use my application as well. The server > will stay the same, but the want to have a seperate database (with the > same structure as the first one). I don't want to copy my > application-files because this would be very unpractible for the further > development. > Unfortunately I have no idea how to realize this. May I put in a > selection field to the loginform, where the user chooses his > organisation? Is it possible that useres of different organisation work > at the same time with the apllication with different databases? Is there > a possibility with the session? > I treasure every hint! > > Thanks a lot > > Rike > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
