I'm in the process of evaluating Turbine for use at a web development
company. I've been looking over the documentation, and I have a couple of
questions that I was hoping that somebody could take a minute to answer
(apologies if I am missing something obvious).
Our need is to develop multiple sites using Turbine, for multiple
clients. Although they may eventually be served from different places,
they will likely have to live on a common server during development. I
don't see anything in the Turbine docs about setting, say, different
database preferences for these different sites. Or ensuring that a user
session from one site cannot bleed over into another.
I assume that I can set multiple class paths in the properties so that I
can keep each site's code separate, but is there a better way of managing
this? Is running multiple Turbine instances possible? Considered
reasonable? Considered to be completely missing the point? What is best
practice for managing this kind of development using Turbine?
Thanks,
Noel Rappin
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
