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 ...Creating a development copy of a DNN siteCreating a development copy of a DNN site
Previous
 
Next
New Post
3/11/2010 4:51 PM
 

OK there seems to be a fair bit of confusion on how to do this.

Here are the steps I take when I want to make another (dev) copy of my live site on a different server.

I'm sure there is more than one way to do it but this how I do it.

Here are the names of servers and services I'll use in the explanation:

wserverlive - live production webserver
wserverdev - dev webserver
sqlserverlive - live db server
iislive - live IIS service
iisdev - dev IIS service
live.com - live portal alias (url)
dev.com - dev portal alias (url)

  1. Go into host > site settings for live.com and add dev.com to the list of portal aliais
  2. go sqlserverlive and make a backup of dotnetnuke database
  3. Now restore the backup you made in step 2 as a different database name - e.g. DotnetnukeDev. At this point you should have a complete file and sql copy of your production system on the dev side.  Now to make it accessible.
  4. go to iislive and copy the dotnetnuke folder to iisdev
  5. Create a new website in iisdev pointing to dotnetnuke folders stored on wserverdev.  Ensure the host headers contain the url dev.com
  6. Setup your dns (or hosts files) so that dev.com points to the IP address of wserverdev.  This will ensure that when you browse to dev.com it will go to the dev server setup
  7. Change the web.config on wserverdev so it points to the db DotNetNukeDev.  Change sql user/role permissions as required.
     

That should be it.  When you browse to dev.com you will go to dev environment (which happens to be a copy of your live environment.  No need to change portal IDs!

I hope this post makes sense and doesn't add more confusion.  Let me know if I've missed a step

regards

 

 
New Post
3/16/2010 1:48 PM
 

Hi,
thanks for the (almost) idiot proof steps.

However, I'm not clear on steps 5 and 6 above? - I can't enter a a dev url.com becasue i want it to straight off the dev server IP address if possible.

thanks, mark.

 
New Post
3/17/2010 1:54 PM
 
Yen Adal wrote:
Hi there, These are the steps I've taken to create a Dev site. 1. On the production site, add a portal alias for your dev site. (e.g. http://dev.site.com) 2. All the steps you outlined above 3. On the production site, remove the dev portal alias That should be it. If you created a whole new parent portal then the contents of the original site doesn't move to the new portal. Different portalID and all hope that helps regards
 

Maybe a daft question, but i'm not sure why i have to ' remove the dev portal alias ' (after step 3)? Will it not work until this is done?

 
New Post
3/18/2010 10:59 AM
 

First time i tried the above the following happened:

 one of my portals picked up the wrong skin and even when i went to host settings >> and changed it back to the original skin it still showed the skin from the other portal.
It was as though the original skin (which was only DNN blue default skin) was corrupted or missing becasue it kept crashing when trying to put back in place. I had created a new database for the development server to connect to and copied all the files on to the development server, so seems a bit strange that when i accessed the development server to check it all worked it affected the live site?

Could it be the portal alias? - is this why i have to remove from the new portal alias initially inputted on the live portal (before backing up and restoring db) from the live site before accessing the dev site?

 
New Post
4/25/2011 3:57 PM
 
I am attempting to do this, clone a site onto my development machine, however, the live site is godaddy hosted, and though I have access to the Admin page, I do not seem to have access to (can't find anywhere), the "Host Settings" or "Portal Page".

I do have access to the FTP of the live site, and a database admin tool.  So my first attempt was to copy all the content, which I simply copied into my C:\Inetpub\wwwroot\mynewsite\ folder.  After doing this, http://localhost/mynewsite DOES bring up the page content, but I can't log into it there, it's not yet tied to the database, which I have restored into my SQL Express, I'm just a newbie here in DNN and not sure how to point the new site to the restored db.

Again, I know this isn't quite the right way to do it, but what can I do without the "Host" menu?

Thank you!
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Creating a development copy of a DNN siteCreating a development copy of a DNN site


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