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

HomeHomeDevelopment and...Development and...Getting StartedGetting StartedBest practice to manage change set in production environmentBest practice to manage change set in production environment
Previous
 
Next
New Post
3/2/2016 2:10 AM
 

Hello All,

I have developed one application using DNN for one of my client. I also have local copy of the site. Now the site is on production server and client is updating the content on weekly basis. 

After few months, my client contacted me to update some of the changes, that i did on my development server. Now i want to deploy my changes to production. So what is the best practice to deploy the update on the existing production site?

I am concerned about the data on production server, what if i deploy the change to production server? Do i first need to update my development server and get the latest data from production server ? How to sync this both? 

Please help me on this

 
New Post
3/2/2016 8:26 AM
 
what kind of changes did you do? Content should be managed in a single place, if you do module or skin development, you should zip your extension as installable package and deploy.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/2/2016 11:32 PM
 

Hello Sebastian,

Thanks for your reply.

We had done below changes on development server.

1. Added fields to custom form e.g Feedback form

2. Added new page to display registered users

3. Added new page to display company policy.

For the above scenario, what we had done is like,

We are just deploying the new pages to the production server instead of whole site and in order to display company policy page, we had uploaded page to production server and then added content from the live site only.

Let me know what we should do in this scenario.

 
New Post
3/3/2016 3:31 AM
 
if you add content or modules, you should perform these actions directly on the production server, unless you are having a custom constellation with specific staging support - this is not contained in DNN core. on the live system, you may use page versions (UI available in Evoq only) and content versions (advanced UI for HTML module included with Evoq products).

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting StartedBest practice to manage change set in production environmentBest practice to manage change set in production environment


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