You could try converting the user models of your applications into ActiveResource's, all pointing to your supervisor application's REST interface.
But in the long run it would probably be best to merge the applications into one, as Marnen said. Instead of having to maintain different databases, deployment strategies, and server setups. On Jan 30, 11:38 am, Heinz Strunk <[email protected]> wrote: > Good evening, > > I've got three different self-programmed Rails application I need to > connect and manage with a 4th "supervisor" application. > > There's a wiki application, there's a shop application and there's a > business directory application all with seperate user database etc. > What I want now is one single user table so it can be all controlled by > one control panel as well as connect the shop with the wiki and business > directory. > > My solution is to programm some kind of a "god application" that handles > all the stuff including the user table for all three sub application. I > just don't really know yet how to do it. > > Any hint, information, suggestions and opinion is highly appreciated. > > Thanks! > -- > 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.
