> 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.
Do you want to store all data for all applications in the same database? If so,
then yes, this is a problem. However, I'd recommend creating a unique database
for each app.
> 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?
>
All of the above can be safely handled by placing each client app in its own
webapp (in Tomcat-speak) or servlet zone (in JServ-speak). (I don't know how
this would apply to other servlet engines.)
> Thanks,
>
> Noel Rappin
>
--
Christopher Elkins
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
