Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN Development and Production environmentDNN Development and Production environment
Previous
 
Next
New Post
5/15/2012 8:32 AM
 
jose rodriguez


Joined: 3/26/2012
Posts: 5

Hi all,

Right now my client is working in DNN version 05.06.01 (238) in his production environment and has two languages. This is the stable environment. He is planning to do mayor changes in the functionality, design and content, so my advice was to create a new test environment with the latest version of DNN and export everything from the production environment and then import all the content to the test environment. The DNN installation is in a virtual server, and I’m thinking to install the latest version of DNN in the same server, so I can have the production environment and the test environment in this server.

Right now I have some questions:

-       Is there any way to export all the content from the previous version and then import the same content to the newer version including containers structure, users, settings and languages? Is there any conflict for doing that using different DNN versions?

 -       Is there any problem in installing two different versions of DNN in the same server (for example registry issues), is better to use to different servers?

 -       What is the best strategy when creating different environments of DNN ( For example Development, Test, Production), in order to make an effective version control of all the element of the content management system?

Thank you and regards,

 Joseph
 
New Post
5/15/2012 9:46 AM
 
jacton


Joined: 3/5/2008
Posts: 51
1. The best way to setup test/staging environments is to just copy the file structure and database of production and restore the database as a new database.

2. It's best to keep the test/staging/production sites on different servers but it won't hurt anything to have them on the same. The reason it is best to be on different servers is to keep things less confusing. You don't want to accidentally make changes to production when you think you're changing test. Also, if for any reason you needed to reboot a test server it wouldn't be an issue, if there are all on the same box then it could be a problem. Finally if you're doing any credit card transactions then it could be a PCI issue having each environment on the same server.

3. Ideally you'd have test/staging/production all on different servers. You do your testing in test, then setup the new content in staging. Once it's approved in staging then you would just copy the files and database in staging over to production.

Justin

Tips, Tricks, and Documentation
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN Development and Production environmentDNN Development and 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