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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Configuration/setup guidelines for websitesConfiguration/setup guidelines for websites
Previous
 
Next
New Post
2/5/2007 8:51 PM
 
As a DNN newbie (but a C# dotnet developer) I have not yet "internalized" best practice/usage. I've been through the forums and doco and played around a bit with a local install. Perhaps someone could advise me on the following (BTW: "website" = business/organization entity e.g. club1, club2, etc).

Should I have one DNN database for all website/portals? One db per website? One per portal (ok - that's a dumb  question right)? I assume at the very least it's one per separate Hosting Service Provider.

What  might some of the use-cases be for portals (parent/child)?  e.g. hosting  logically seperate website within a single host (perhaps multiple clubs in a single "framework" providing SSO and shared "features").

I'm thinking that there can be m-m correspondence between websites and domains but one portal per "website"??.

The DNN 4 book probably answers all this - but it's a few weeks away.

Apologies if the above is a bit confused - it's because I am .

thanks
 
New Post
2/6/2007 3:52 AM
 

a portal is a synonym for web site. DNN multiportal feature allows you to create a large number of portals using the same installation files, all portals will share code (including modules), database and host settings, but are separate apart from this and shall usually not interfere at all (there is a limitation: the same username cannot be used in multiple portals of your installation except with the same passwort).

The decision, whether to user a single installation for all portals or multiple portals with separate installations depend on your business model. a single installation is easier to handle and has less server requirements, but if a web site grows and needs dedicated resources, it is a lot of work to separate it. on a shared installation you cannot backup/restore single portals, only all of them.

Child portals are usually used for projects, divisions, ... that use the same domain address (with a folder name added) but a separate membership and management. In many cases it is also possible to use a subdomain (myproject.mydomain.com) with a parant portal instead of using a subportal (www.mydomain.com/myproject).

HTH


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/6/2007 4:15 AM
 
Thanks Sebastion

thats very helpful. Clear and concise.

I've also found what looks like good tutorials to work through at http://www.dnncreative.com/Tutorials/DNNTutorialsforAdministrators/MultiplePortals/tabid/300/Default.aspx

cheers
bruce
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Configuration/setup guidelines for websitesConfiguration/setup guidelines for websites


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