I'm looking for the best way to deploy DNN for a corporate internet website.

I would like to utilize both development and production web servers, and am curious to know the best way to accomplish this. I was thinking of installing the Source package on the development server, and installing the Install package on the live web server. I would like to be able to add and /or modify modules, which is the reasoning for wanting the Source package on the development server...and I was thinking that'd it'd be better to have the Install version of the application on the production web server.

Is there a clean way of creating a portal on a development web server and then rolling it out to a production web server?
I would like to create the website on the development server, and then deploy the entire site to the production web server. Could I accomplish this by doing a backup of the development database, and then doing a restore on the production server database?

The main thing I need to know is how best to set-up a website with DNN (on a development web server), and then roll that website out to a production web server. Also, I have complete control of the web servers, so there will be no hosting issues.

Thanks in advance.

- Doug

You do not need to use the Source version at all. You should only make modules and for this you only need the Install version.

To make changes to modules you simply upload the changed module to the Production server.

To move content see: IPortable: Easily export DotNetNuke® content from your module to deploy on your production server (in VB.NET and C#)