Last post May 24, 2005 11:09 AM by Noel Jerke
May 24, 2005 07:48 AM|eureka|LINK
I have searched for the answer to this question as I am sure it must have been asked before, sorry but as yet not found it.
Is it possible to run more than one copy of DNN on one computer without causing conflict?
I would like to use one copy at a test site. One copy /site for myself and one separate copy/site for a friend.
According to every installation instruction that I have read, each new install of DNN follows a strict naming convention, i.e. dotnetnuke for the root folder and also the virtual directory name in IIS, how can
I get around this?
Thanks in advance.
May 24, 2005 10:27 AM|matchbx27|LINK
DNN is very flexible and can be set up several different ways. If you are doing everything locally the easiest way to have two folder each with the DNN folders and files. The root folder does not have to be named Dotnetnuke. The Web.Config in each root
would be configured for a different database.
<add key="SiteSqlServer" value="Server=(local);Database=dnn1;uid=xxx;pwd=xxx;" />
<add key="SiteSqlServer" value="Server=(local);Database=dnn2;uid=xxx;pwd=xxx;" />
This way each DNN installation (the files and folders) would point to a different database. Keep in mind you still have to create the database prior to executing the installation.
If you only have access to one database you can change the ObjectQualifier (found in the Web.Config) so you can run multiple installs off the same database.
May 24, 2005 11:09 AM|Noel Jerke|LINK
The way I do multiple installs is as follows:
- I setup a new folder for DNN
- Go into IIS and setup a new website or virtual directory for that DNN folder
- In SQL setup a new database for that install of DNN
- Change the web config for your new DNN install to point to that database
You are on your way then! As mentioned in the other post you can also setup multiple versions of DNN in a single SQL database with different object qualifiers.