[ic] best set up with several stores

[Dan B]

At 10:32 AM 2/27/2001 -0500, you wrote:
>Thanks for your quick response.  Currently, I have installed interchange
>into two separate directories.  (Each directory has its own apache
>httpd.conf file, too.) So my directory structure is as follows:
>
>/web/sites/store1/(interchange root, also cgi-bin, etc)
>/web/sites/store2/(its own interchange installation)
>
>I can get store 1's interchange server running, no problem.  By doing
>/web/sites/store1/interchange/bin/interchange -r  (as the interchange user
>of course)
>
>But when I go to start up an interchange server for store 2, it won't start
>because it sees the other one running.  Therefore, right now I can't get two
>interchange servers running.

unpack .tar.gz
./configure
tell it to install to /web/sites/store1
run /web/sites/store1/makecat
(finish setting up catalog)
/web/sites/store1/interchange/bin/interchange -r

then

./configure (2nd time)
tell it to install to /web/sites/store2
run /web/sites/store2/makecat
(finish setting up catalog)
/web/sites/store1/interchange/bin/interchange -r

That works fine for me, I hope it helps.

>I'm just wanting, currently, to run one apache server & interchange server
>per catalog (aka store directory).  That way our developers can restart
>whenever they need to update information etc. without affecting other
>stores.
>
>Help - Thanks
>
>
>----- Original Message -----
>From: "Mike Heins" <mikeh@minivend.com>
>To: <interchange-users@lists.akopia.com>
>Sent: Monday, February 26, 2001 11:56 PM
>Subject: Re: [ic] best set up with several stores
>
>
> > Quoting Dan B (db@cyclonehq.dnsalias.net):
> > > Yes, you can also easily run multiple interchange deamons per box.  Just
> > > install them to different directories (/usr/local/ic-4.6.3,
> > > or  /usr/local/ic-CVS-$DATE is how I do it).  It doesn't hurt for them
>to
> > > share a common catalog directory (such as /var/ic), but you probably
>don't
> > > want two daemons accessing the same catalog at the same time :-)
> > >
> >
> > Actually, that is not a problem. It isn't really any different than
> > different users hitting the same catalog with browser clicks on the
> > same daemon with forked children. We are very fussy about locking files,
> > which accounts for Interchange's good reputation for robustness. 8-)
> >
> > In fact, I recommend this. Make one daemon with the UI for your admin,
> > protecting it with HTTP basic auth and/or allow-deny IP/host statements
> > in the web server, and disable the UI in the production version that
> > customers use. This is much more secure as all of the GlobalSub and
> > UserTags that modify files are out of play.
> >
> > (You might have to include some of the UI usertags from lib/UI/usertag
> > if you employed them in the catalog -- the only one I can think of that
> > we use in the demo is [button ...] and maybe [table-editor ...] in the
> > DEV_4_7_0 branch.)
> >
> > I will try and include instructions and a little batch file to do
> > that in the next release.
> >
> > Best,
> > Mike
> > --
> > Red Hat, Inc., 131 Willow Lane, Floor 2, Oxford, OH  45056
> > phone +1.513.523.7621 fax 7501 <mheins@redhat.com>
> >
> > Be patient. God isn't finished with me yet.  -- unknown
> >
> > _______________________________________________
> > Interchange-users mailing list
> > Interchange-users@lists.akopia.com
> > http://lists.akopia.com/mailman/listinfo/interchange-users
> >
>
>
>_______________________________________________
>Interchange-users mailing list
>Interchange-users@lists.akopia.com
>http://lists.akopia.com/mailman/listinfo/interchange-users

Dan Browning, Cyclone Computer Systems, danb@cyclonecomputers.com