Hello to All reading this,

I'm new to DotNetNuke and am trying to figure out the best way to set up it up. My initial setup was using MS WebMatrix primarily for evaluation purposes. I downloaded DNN Community and it installed fine using local host and the SQL Express. I created a new web site with several pages and skins I had downloaded. Runs fine on the local host. Now for my questions.

I have ASP host that can run the web site and for that matter multiple web sites, but I'm trying to figure out the best approach for ongoing maintenance and for giving a client access to the site to make certain changes.

1. Should I install DNN on the web host and do the development there for all the web sites and use my PC for backup purposes or
2. Continue to develop on my PC and publish to the web host.

What would be considered the best practice here? If you could direct me to some documentation, papers, blogs, whatever .. on this subject it would be appreciated.

Cheers,
Larry

If you are talking about module or skin development, then the best process is really to work locally - however if you are talking ongoing development for a live site - then really you reach a point where you need to develop on the live site - as there are logistics involved in updating a running live site from a backend development server.

Once a site is live - especially a dynamic one with end users doing updates - then there is no easy workflow to push changes live from a development server as well - you can do database back ups and restores as this could potential wipe changes made on the live site - even simple changes like a new user added or a role changed.

Westa