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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Maintaining and evolving a DNN siteMaintaining and evolving a DNN site
Previous
 
Next
New Post
4/17/2007 1:31 AM
 

I'm a stone-cold newbie here, so pls excuse me if the the answer is obvious to all but me...

Most commerical sites, I would think, have at least two versions:  staging and production.  How do most folks matintain and evolve their DNN sites?  Do you modify a staging server, then copy your site over to a production box? With a database-based system like DNN that would probably require some DB scripts at a minimum.  If this is the approach, is it straightforward to copy just "content" over to production [as membership data will be changing in realtime]? 

Or do people actually modify the production site?  Sounds scary to me.  I must be missing something fundamental here.

Is there a programmatic way that is non-obvious to "port" just changes from staging to production?

thanks,

ak

 

 
New Post
4/17/2007 9:28 AM
 

I made a post about this at the end of this thread:
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/118/threadid/101235/scope/posts/Default.aspx

Basically: DNN is a CMS... this means that the live site is the primary site... there is no staging server for content. Staging for content is a sign-off process that is made obselete by the design of your sign-off workflow within the CMS. Risk to this content-data is dealt with by your backup procedures.

Now.. that only covers the site owners' content. But, what about your code?... to test your code modifications, you make a duplicate portal. Install your updates, assess your modules, try out your code changes in that. When you have ascertained that your code is flawless on this duplicate server, migrate the change to the primary portal. You might have a scheduled outage for this if your site is popular and the changes require downtime. By Migrate, I mean carry out the changes in duplicate. E.g. if you were testing a new module and it worked flawlessly on your duplicate portal, then you can install it on the live one. All of this requires good procedures and accurate record-keeping... no stuffing around.

Regards,
Rob

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Maintaining and evolving a DNN siteMaintaining and evolving 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