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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...merging DEV and LIVE sitesmerging DEV and LIVE sites
Previous
 
Next
New Post
6/15/2010 12:55 PM
 
Hi

For a while now we've had a live site with data going in, event, pictures and text and documents being added in various modules.

We now have the problem of how to develop for this site and to get the DEV versions back across to LIVE.

If we take a new clean version of LIVE by the time we've finished configuring a new module and adding all the pages then the LIVE version has moved on.
We're really struggling to find a safe way of working.

If it was just the DB we might be able to do a merge but what about files and modules and versions?

Anyone got any pointers?

thanks
Gus

"if the only tool you have is a hammer you tend to see every problem as a nail" http://www.carawaydesign.com
 
New Post
6/16/2010 4:54 AM
 
one option is cloning live site for dev, update dev site and copy content on database and file level - however, this requires a deep understanding of file and database structures used by the core framework and each module. another option for custom module/skin development is package and install: develop module function and skin desin on the dev server and package these extensions as if you would like to offer them to clients. For content of modules, which support iPortable interface, you may use export/import level on module action menu.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/16/2010 5:11 AM
 
thanks Sebastien

the first option is way to dangerous for us I'm afraid!  And I've not had a lot of success with iportable with third party modules over the years and don't trust it.

The way we hope to get around this in the short term is:

1> back up everything!
2> copy live to DEV server and develop on that making careful notes of all changes.
3> create a third staging site.
4> When we go live we stop all work on LIVE and copy to staging site.
5> Implement all changes from DEV onto staging site
6> copy staging site to LIVE.
7> go down the pub to watch the football

or

8> end of with a terrible mess and spend all night trying to put it right..


gus

"if the only tool you have is a hammer you tend to see every problem as a nail" http://www.carawaydesign.com
 
New Post
6/16/2010 5:11 AM
 
thanks Sebastien

the first option is way to dangerous for us I'm afraid!  And I've not had a lot of success with iportable with third party modules over the years and don't trust it.

The way we hope to get around this in the short term is:

1> back up everything!
2> copy live to DEV server and develop on that making careful notes of all changes.
3> create a third staging site.
4> When we go live we stop all work on LIVE and copy to staging site.
5> Implement all changes from DEV onto staging site
6> copy staging site to LIVE.
7> go down the pub to watch the football

or

8> end of with a terrible mess and spend all night trying to put it right..


gus

"if the only tool you have is a hammer you tend to see every problem as a nail" http://www.carawaydesign.com
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...merging DEV and LIVE sitesmerging DEV and LIVE sites


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