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...Best practice for moving through environments.Best practice for moving through environments.
Previous
 
Next
New Post
1/24/2007 1:56 PM
 
I’ll be up-front here and say my experience with DNN was none prior to taking my current job, is probably slightly above elementary now, but is rapidly growing. So that being said, go easy on me if I’m bringing up a topics that has already been covered. (I’ve have spent extensive amounts of time reading through the forums looking for solutions…I swear!!)
 
To the point of this post; I have and would like to maintain a Development, Certification/pre-production and Production environment with a smooth and well documented migration process. As of right now it looks like this, Dev and Cert are hosted on one box, under the same DNN install. This is accomplished by having two portals, DevAppNamePortal and CertAppNamePortal. Production is on a second production box. Development will truly be a testing and development environment. It will never be migrated into Cert as a whole, only bits and pieces. Once I’ve tested a module or whatever to my liking I’ll recreate it and put it where I want it in Cert. Once it has been tested and “certified” as working it will be migrated to production during a change window. Using this process you can see how it’s crucial that I take an exact copy of Cert and apply to Prod. Currently the person in charge of our web presence (and DNN by circumstance not choice) has encouraged me to export the content of each individual module, then use the import which means I basically recreate the entire site. This is time consuming and error prone considering the limitations of the export/import tool. There are too many opportunities for me to over look a setting or flat out miss something.
 
It seems that there would be others out there who have solid, real-world experience with this same or similar configuration. (and if you’re not using separate environments for development and production data, please let me know where you work because I’ll be applying for your job after some random change you’re testing wrecks your site and the boss/client flips…haha!)
 
The only idea I’ve come up with (have not tried/tested) would be to do a complete backup of my Cert portal then restore it as the Prod portal. I can already see a couple short comings with this process, but lacking another solution I may be stuck trying to make it work. In a more, I’ll call it traditional setup I’d just copy the site, change any Cert references to Prod, drop the site into production then go have a cold beer because my work is done…
I don’t see how I can do that using DNN but hopeful there is something that will help me.
 
Thanks for your help.
 
-r
 
New Post
1/29/2007 11:18 AM
 

Surely someone is using more than one environment and has run into this issue? Surely you guys are developing the DNN stuff in a similar manor??

-r

 
New Post
1/29/2007 11:50 AM
 

Yeah, in DNN there can be issues migrating individual portals from one server to another due to the openness of DNN.  You might look signing in as host, selecting portals and export portal as template and then select to include content, not sure if there are any red flags with this though. 

One problem though is if you use a module that does not support import/export, it may not migrate.

For me, I just work directly on there server where my changes are not visible to the users until it is finsihed and tested.  This obviosly cannot cover all situations, but it is what I do most of the time.  Other times I can import/export the parts that need to be moved or I will script parts to/from the database.

Maybe there are others here though that have it more streamlined ;)

 
New Post
1/29/2007 11:44 PM
 
I've been meaning to post this comment for some time now so here it is.
 
Use of a content management system, such as one can build using the DNN application framework, requires that one be more specific about what a development server is actually for. The old methodology of applying both technology and content first to a development and then to a live server is just not valid and is also difficult to implement and maintain. 
 
Think of these as separate things:  
  1. Content (Business)
  2. Technology (IT)
  3. Content and technology data (IT)
And manage the risks as follows:
  1. The accuracy and compliance of content is maintained by the secure and complete publishing work-flow you devise for the content creators.
  2. The suitability and security of web technology is assessed and developed away from the live site on a development server.
  3. Content and technology data safety is provided by the backup and restore procedures - same as all the other data in the office.
Therefore:
  1. Run a development server for technology development purposes, e.g. building and testing modules.
  2. Develop content sign-off work-flow within the CMS (after all, that's what it's for) and leave it there to be carried out in real time, on the live site by the users who are assigned to do so.
  3. Back it all up.
DNN is a tool for building real-time interactive websites. It's your job in IT to make sure it provides the desired functionality, runs well, is secure and is always backed up.
 
You should definitely do your own learning, testing, development and all other assessment work on a separate server rather than the live server. The live server is for your users... the development server is for you.
 
If you're wondering how to apply your latest developments to the live site: Just do it. You already know it will work because you've followed the correct testing procedure.. right?
 
Regards,
Rob
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Best practice for moving through environments.Best practice for moving through environments.


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