Rails - Sep 2005 - Sharing models between two applications

Hi !

I have two applications - one is a front end, the other is the admin 
application for the front-end.  How should I share my models between 
both applications ?

I''m thinking that a simple svn:externals should do the trick, but maybe
other people have other ideas.  What about a productized Rails app ? 
Would that do the trick ?  I don''t think this would apply in my case.

Thanks !
François

François Beausoleil wrote:
> Hi !
> 
> I have two applications - one is a front end, the other is the admin
> application for the front-end.  How should I share my models between
> both applications ?
> 
> I''m thinking that a simple svn:externals should do the trick, but
maybe
> other people have other ideas.  What about a productized Rails app ?
> Would that do the trick ?  I don''t think this would apply in my
case.
This may seem like an obvious question, but do the two apps need to be
hosted separately?  Just from your brief description, it sounds like you
want separate controllers in the same app.

If that''s overly simplistic, how''s this for a blue-sky idea: 
host the
models in one app (which obviously must take care of the database
connections), and export them to the other over DRb?  Has anyone tried
that before?

-- 
Alex

Hi !

My problem is that the frontend application needs the whole URL space 
available - I can''t reserve anything for the app.  My routes look like
this:

map.connect ''*path'', :controller =>
''server'', :action => ''view''

That is the one and only route in the application.  The backend 
application on the other hand has the regular routes - 
:controller/:acton/:id.

Alex Young said the following on 2005-09-28 03:50:
> This may seem like an obvious question, but do the two apps need to be
> hosted separately?  Just from your brief description, it sounds like you
> want separate controllers in the same app.
They don''t need to be hosted separately - just on different domains: 
app.com/ and admin.app.com/
> If that''s overly simplistic, how''s this for a blue-sky
idea:  host the
> models in one app (which obviously must take care of the database
> connections), and export them to the other over DRb?  Has anyone tried
> that before?
Seems a bit too heavyweight for my needs.  At the moment, I am 
everything I can using svn:externals  lib/tasks/, vendor/, app/models/ 
and db/.  Works fine for now, and it was a simple, quick solution to the 
problem - KISS and DRY to the rescue :)

Thanks for your input.  Might use that one day.

Bye !
François