Hello all. I currently have an OpenACS site and a static site, set up
as virtual servers, being handled by the same instance of AOLserver
2.3. I want to put a separate OpenACS environment behind the static
site, and eventually serve other OpenACS sites on the same machine as
well.
My thinking is to set up the separate sites with separate instances of
AOLserver, each with it's own .ini file.
It looks like this goal can also be accomplished with virtual servers,
setting up database pools main1, main2, subquery1, subquery2... for
the entire server, then hooking the main pool for virtual server 1 to
main1, etc. The downside I see to this approach is that multiple
ad.ini files need to be embedded in the single AOLserver file, making
maintenance a little trickier.
Is one approach preferred over the other?