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 ...Newbie: DNN5: how to move a site from dev.domain.com to www.domain.comNewbie: DNN5: how to move a site from dev.domain.com to www.domain.com
Previous
 
Next
New Post
1/24/2009 2:17 PM
 

Hi,

As we are new to DNN I created dev.domain.com as a new hosting on our plesk server, linked DNS to it and named the DB DNNtest...

As our designer is getting along I will get to the point that the new DNN site will need to replace the live site on www.domain.com. The currently live site (static HTML) is hosted on the same plesk server but on a different hosting, with separate FTP id and so on.

I did find some articles about transfering sites and from one ISP to another, but not from one hosting package to antoher on the same server.

Now I learned by using it that plesk is a bit more complicated then expected, and am caught scratching my head frequently.

Some headscratchers;

1. Transfering should be quick, I should be able to change the header from the old site to the new one within plesk, but how will DNN react to that, I assume much is linked to dev.domain.com and just changing the header wont fix that.

2. Could I take a backup of the DNN site on dev., create a empty DB on the www. hosting and quickly delete the contents there and restore the backup to it?

3. I've learned DNN can hold many portals, so you could host many sites on one installation. How commonly is this used in 'the field'. I could imagine that when  a user on portal 201 writes some crappy code, all sites on that DNN could crash?

 
New Post
1/24/2009 9:43 PM
Accepted Answer 

Hey Jurgen,

Jurgen Verhelst wrote

Some headscratchers;

1. Transfering should be quick, I should be able to change the header from the old site to the new one within plesk, but how will DNN react to that, I assume much is linked to dev.domain.com and just changing the header wont fix that.

In addition to changing the header, you'll want to create a new portal alias for your portal. You can do this from the Host->Portals page (near the bottom once you "edit" your portal - you'll see the header "Portal Aliases" and can "add new alias" from there).

Portal Aliases are used by DNN to map the incoming URL to a particular portal - this way DNN knows which one to use. Without creating a new portal alias, after updating the header in Plesk, when you access the new URL, it will redirect to the old portal alias.

2. Could I take a backup of the DNN site on dev., create a empty DB on the www. hosting and quickly delete the contents there and restore the backup to it?

You can certainly take a backup of the database and restore it elsewhere. DNN is an asp.net application like any other and allows for (relatively) easy movement. Make sure you backup the complete filesystem (the entire root of your website) and also the complete database. There are settings in your web.config that must match that of your database, so you can't go mis-matching the filesystem and database.

3. I've learned DNN can hold many portals, so you could host many sites on one installation. How commonly is this used in 'the field'. I could imagine that when  a user on portal 201 writes some crappy code, all sites on that DNN could crash?

This happens in the field quite frequently, but really that's irrelevant, because it's all about what is right for your particular needs. If they are "small" sites that are not mission-critical then having multiple portals within a site may be fine. But if it is in any way mission critical, I'd suggest splitting them out. Of course this means managing them will be that much more complex. Bottom line is that it is more simple to share portals, but not nearly as configurable (or complex).

Hope that helps,

Ian


Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
New Post
1/29/2009 5:00 PM
 

Hi Ian,

Thanks a lot for the information. I'll try it on a test setup first.

Regards,

 

Jurgen

 
New Post
6/14/2010 2:04 AM
 
Hi Ian,
With regards to:

2. Could I take a backup of the DNN site on dev., ....

[/QUOTE]

You can certainly take a backup of the database and restore it elsewhere. DNN is an asp.net application like any other and allows for (relatively) easy movement. Make sure you backup the complete filesystem (the entire root of your website) and also the complete database. There are settings in your web.config that must match that of your database, so you can't go mis-matching the filesystem and database.


We are currently trying to complete a move to a new hosting provider and they are not yet prepared to restore the MSSQLDB.bak.

I have made adjustments to the connection string in preparation for the new DB.

What other steps can be taken to circumvent this pitfall or how do I repair if the restored DB fails?

Thanks in advance,
Mike
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Newbie: DNN5: how to move a site from dev.domain.com to www.domain.comNewbie: DNN5: how to move a site from dev.domain.com to www.domain.com


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