Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Best Practices regarding multiple sitesBest Practices regarding multiple sites
Previous
 
Next
New Post
3/18/2008 9:12 PM
 

What is the best practices philosphy regarding the hosting of multiple websites. If each website hosted is separate and distinct from the other is it recommended to have a separate database and therefore a separate install for each website or to have a single install of dnn and host the variety of websites within it. Though I am concerned about the users table as everyone is stored there. Or is this no big deal? Just a little confused and some clarification / discussion is appreciated.

Thanks.

 
New Post
3/18/2008 10:56 PM
 

We stay away from running multiple websites on one DNN install, especially for paying clients. I can only think of very few instances where multiple sites on one DNN install actually makes more good than harm. My biggest issue is the single point of failure that it creates.


Tom Kraak
SEO Analyst
R2integrated
 
New Post
3/19/2008 8:47 AM
 

Same here. We stay away from multiple portals on the same DNN installation. There are a lot of reasons for this.For example what if one portal want a module that conflicts with a module another portal uses.If you update the core dnn or some modules all portals might need to have their skin updated at the same time.One portal might affect the others in some way (However unlikely but they do run from the same asp.net install). If one get overloaded the others will die with it. What if one portal have to edit the default.css file (Since it contains a lot of specific tags like H1, lu, li and all the rest).

 
New Post
3/19/2008 10:04 AM
 

If you need to share users, you need the same database/install.  As a user, you can run multiple sites under one install, as parent or child portals, usually because your host only allows a single database.  As a host though, this doesn't make sense.  Each account gets it's own install and database.  As a commercial web developer, never share anything between clients.  Clients don't like it.  :)

Jeff

 
New Post
3/26/2008 10:07 PM
 

Thanks for all of your input. I began to realize this after I noticed all of the users from different websites stored in the same users table. Now to split my portals up into their own sites.... niiiiiice.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Best Practices regarding multiple sitesBest Practices regarding multiple sites


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out