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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Development and Production EnviromentDevelopment and Production Enviroment
Previous
 
Next
New Post
1/31/2006 7:06 AM
 
Hello,
Can anyone give a glace on best practices for developing in 2 separate enviroments! I have some questions about how i should do this..
  • What package should i install on the production server? The "Install" package right? And on the development server i should be working with the "Source Code" package!
    • What if i use the 4.02 version? Should i use the "Starter Kit" in any enviroment?
  • Witch are the best ways for developing modules and then pass them over to the production server! How can i improve the task of altering modules or skins in the develop server and pass it over to the production?
Thanks,

Nuno Costa
 
New Post
2/1/2006 8:21 PM
 
Hey Wolf, I don't know if there are any official "best practices" but I can tell you what the folks at PowerDNN do and it works out pretty good.

What they do is set up two sites that are identical except that they are using different databases.  When a client wants to do something, they can try it out on the dev version, and then if everything works out good, they can push the changes over to the production version.  It works out pretty good because you never end up killing your site.
 
New Post
2/2/2006 6:30 AM
 

My question is how do you " push the changes over to the production version"? In the production server you have the "install package" and then you copy the files and install developed modules, is that it?  What files do you copy?

 

 

 
New Post
2/2/2006 10:27 AM
 

The way I've got my stuff set up is like this: 

Dev site installed from source with all of the source code from each individule project. There I can make changes to code and build as I see fit and have full debugging availble.

Live site originally installed from Install_PA configured and working well.

Now say I want to fix the issue with the gallery being unable to change skins.  I go to me Dev system make the changes, compile and test.  If all is well I can either copy the one dll that changed in the module to the live site or I could create a new Gallery-Install_PA zip file and install that on the live server. I generally just copy over the dll that changed.

For bigger changes like going through all of DNN and changing the datacache.getcache if structures, once it's all compiled in release mode and tested completly I backup the live bin directory and then copy all of the new dll files over to the live server from Dev. But probably should create a new install package and copy over everything. :)

Cheers, 


Paul Davis
 
New Post
2/2/2006 11:08 AM
 

Yes i undestand!

Just one more question... But if instead of changing an existing module, what if you had a completely new module?

Just copying the dll isn't enought right? I'll have to copy the folder with the controls and add the new definition! Or make a module package!

This job of adding a new definition must be done also when you are developing the module!

When you change a module in development you dont have to erase the older definition and then add the new one, do you ? Maybe adding a ascx, but the definition (and the relationship with the pages) are the same!

 

Complements,

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Development and Production EnviromentDevelopment and Production Enviroment


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