Dotnetpanel Forums

 New to DNP, and looking to community for some guidance.

 What is the best way to work with DNP in order to support a "development" site and a "live" site?  For instance, if Example.com were hosting with us, and the owners wanted to redesign the site, we'd setup a new site under "dev.example.com".  

Once the website on dev.example.com were completed,what would be the best way to make those changes "live" for example.com?  Keeping in mind that we might have setup new databases for dev.example.com that are not on Example.com...

Did I explain that well, or is that confusing?

I must admit, I'm also very curious on how this should be achived using DNP (as a customer, not admin).

For clarification; I think this is what you mean:

• You have two websites (two seperate in DNP and on the IIS).
• live: the live website
• dev: the development website
• you have a few DNS records assigned to the live website
• For example: www.example.com and example.com
• you also have a DNS record on the dev website:
• For example: dev.example.com
• When the development is finished on the dev website you want to move www.example.com and example.com to the dev website, so that it will start to act as the new website for example.com.
• I presume that the development of this new website (dev) is done i a completely new application, that is; there is now chance to run the new website with the olde since they are not using the same application (for example DotNetNuke)?

Otherwise, if there is no feature for this in DNP (which I feel there should be), the only way you do this is by editing the IIS configuration; changing the host-headers of the websites.

.. I'm also presuming that these two websites are running in the same IP and server..

.. this also reminds me of another feature I'd like to have in DNP:

The possibility to edit the DNS records in more detail. Especially the TTL of DNS records.

 What I do, is to setup a seperate account for that purposes - so I have 2 accounts, one for developement, and one for for the live site. If you're looking for a way to offer this to clients, then they could easily setup another domain in their account, but make it a subdomain (helps with the DNS stuff :) )

 So, their main account is www.livesite.com - then create another website, called dev.livesite.com - and use that for development