I do understand the Multi Portal Idea of DotNetNuke and YetAnotherForum. But. Wouldn’t it make more sense to install a separate install (dnn code base) into a separate folder for each client (on the same server)? That way if one portal (dnn install) gets messed up, they all don’t go down with it!
For example.
CompanyA -comes to you and wants you to host DNN and with YAF. Wouldn’t you want to install this companies DNN code into a folder of its own. (Separate database too, maybe called companyAdnnDB and a separate YAF database maybe called companyAyaf.
CompanyB -comes to you and wants you to host DNN with YAF. Wouldn’t you create its own folders/install directories/databases? say.. a folder called companyBdnn and a database for them called companyBdnnDB and a YAF database called CompanyByaf.
I do understand that if you create and upload modules, you’d have to do it for each client (code base/dnn install).
But backing up the client’s data, and keeping things clean, seems better this way. Say a client wants a copy of there data or database, it seems like it would be a huge task to strip out all data from everyone else before sending the client the database (if that is a service)
Each company could, create sub portals for their install (using the dnn menus), but companyA's install of dnn and yaf would have nothing to do with companyB’s install of dnn and yaf.
I have it setup this way on my server. it seems to work well. This way, I can install code/modules/skins.. to a default install of c:\dotnetnuke and yaf. If the install goes well and the site doesn’t crash or goof... I then install the module into the clients (company A and B) code base of dnn.. (logging in as host)
Does this make sense? is it over kill? it just is nice to have a c:\dotnetnuke separate code base to play with.. and mess up.. Without taking down clients installs of dnn.
Thanks.. Comments please..
AskHottie.com
http://www.AskHottie.com
.COM with US!