From: d c Date: 2007-12-15T17:04:12+09:00 Subject: Re: Looking for a new web framework. I've had problems with code re-use on view-level across rails apps. plugins have their limits. you could look at rails engines to set up a core shared app, and/or plug-abble apps - which allows you to basically make one app a plugin to another parent-app so you can override the needed areas on a per-app basis. plug-apps hasnt been active since april tho, and no support for rails 2 seems to be forthcoming. engines is similar but slightly more active. both have big detractors in rails community, but there is no other obvious solution for code sharing other than building a monolithic app with multiple entry points. /dc On Dec 15, 2007 4:54 PM, Tim Uckun wrote: > > Maybe I'm missing something, but it sounds like Rails would work great > > for your situation. > > > > > If rails can work for me I don't quite know how to do it. Let me explain. > > I am about to start a project which will involve creating several web > sites. These will be completely different web sites but for the same > company and using the same database. > > I can already forsee that I want to share many (but not all) of the > models between the web sites as well as sharing some of the > controllers. > > I am not sure how the views situation will work itself out yet but to > start with I would like to set a "master" template that every web site > uses and override individual sections and content using partials. > > > Ideally it would be a kind of a hierarchy where I had a /websites > directory with each rails app living underneath it. If I called for a > model it would look in /websites/myapp/app/models and then look up > /websites/shared/models if it could not find it. Same with > controllers, views etc. > > It would also be nice to use same mongrel pool for all the web sites. > > > I hate to say it but something sort-of-kind-of-but-not-really-zope. > >