Hi,

I wanted to know there is an easy way of deploying two instances of dot net nuke on a server or two with both of them pointing to the same database.  What I need is a Content Management System which can share the contents among its instances, but keep the permissions on the users separate.  For example, a user uploads content through one of the instances but the settings are different so an anonymous user of instance A will be able to see the content whereas an anonymous user of instance B would not be able to.  I'm not too fluent in dnn, can someone enlighten this newb?

Well, we are actually doing something similar to this where there are two IIS instances that point to the same database.  However, the separate instances point to separate parent portals so they do not respond to anything else but their host alias.  Plus they are on separate IP's.

We do this because we implement a different provider for membership (custom/legacy vs dnn) than the other.   However, the maintenance of two DB's adds much more complexity than managing two web.config IMHO. 

Maybe we are doing it wrong but this is one of the powers we found to using it.

-Chris