Instiki devel - Oct 2005 - Integrating i2 with other rails apps

I''ve been working on a "directory" style Rails application
for a
community organization (i.e. something that keeps track of names and
addresses and produces a directory). I''ve also been looking at setting
up a wiki for them, and had been dithering between the available
options (looking mostly at TikiWiki and Mediawiki).

Now that I see i2, I''m kind of tempted to use it instead of one of the
more "ful-featured" options. The reasoning would be that I''ve
got some
chance to understand what''s going on in i2 and customizing it (or at
least a better chance than many of the alternatives).

I guess my question is an architectural one. How does one go about
integrating multiple Rails applications? In theory, I suppose I could
probably run my Directory application (for instance) alongside i2 and
get Apache to invoke the correct app based on the first part of the
URL. However, this seems to cut down on the opportunities to integrate
the two.

Alternatively, I could run them both as the same application -- that
is, starting with a plain i2 and then adding what had been in my
Directory application (and whatever else I develop). Essentially,
then, the server would be running only one Rails app, and I would just
keep customizing it with whatever I add.

I guess what I''m asking is whether I seem to be thinking this through
properly. What I''m tempted to do is construct one Rails application
that incorporates whatever I think is useful (including i2 and
whatever I custom develop). Is that a sane option, or should I be
thinking this through differently?

Ryan Rempel wrote:
>I''ve been working on a "directory" style Rails
application
>  
>
Hi,

You should really ask this question on rails at lists.rubyonrails.org
You can totally mix two apps within the same directory structure. The 
only points where they cross will be config/routes.rb, 
app/controllers/application.rb and app/views/layouts/default.rhtml, and 
none of thoise are difficult to reconcile.

Alex