Hello, I have a rather strange configuration I am trying to work out.

What I want to do is host several sites on a single DNN instance, each site will have their own IP address, and SSL certificatate to encrypt the site (or at least the logon).  I do not want to share the same certificate for every site and I dont really want to install dozens of seperate instances of DNN in order to do this.

So my questions.  Is it ok (safe?) to point multiple IIS websites at the same DNN directory and SQL database? If so, are there configuration details I need to pay attention to in order to make this work right? (App pools, scheduled tasks, etc)

 

Thanks

As mentioned above that shouldn't be an issue at all!

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

I used to have all my DNN sites run under a single instance/installation. Reason was I wanted to be able to easily keep ALL sites updated easily.

But one major issue I found was that the database swelled like crazy. And it is really a daunting task when migrating to a different server should one particular portal owner (out of many) decides to do so. So now I go back to 1 DNN instance per site.

---

Warm Regards,

Ed Borhan [ evolve | build | connect ]

A DotNetNuker Since 2005 (v 03.00.11)

Ed Borhan > adaptive webware
Think Gold Internet (TGI)