Last post Dec 20, 2005 10:36 PM by aus_nexxus
Dec 20, 2005 09:37 PM|pmaugust|LINK
Not really a getting started, but more of a "staying started" post. I have a couple of questions about the care and feeding of DNN in support of a production site. Hopefully someone has some simple answers. [Idea]
1) Release numbering. Any significance? Is it like Linux used to be (is?). Anything with a .even number (0, 2, etc) was considered the current "stable" release. Odd numbers (.1, .3, etc) was the current development release? Basically, what is the release
2) What is best practice for upgrading so you can roll back? Say you are at 3.2.0 and running well. What's the best process to implement 3.2.1 so if it has issues you can't work around, that you can get back to 3.2.0 core without losing data?
3) Is there a good process for copying a site? For example, you have your production portal, and you want to try some new things (new core upgrade, new module, etc). What I'd like to do is take the exisiting site, package it up and install it on a QA instance,
test the new functionality (making sure I dont break what already exists) and then if all is well, apply the upgrade back to the production site, and removing the QA site until a next upgrade time?
With any process I ever worked with, I've always had 3 versions, Prod, QA (snapshot of prod with upgrades), and Sandbox (try anyting you want here). I'm trying to figure out the best way to implement that kind of process with DNN. Any suggestions?
Thanks in advance,
Dec 20, 2005 10:36 PM|aus_nexxus|LINK
1) We only release stable and tested releases and do not have a development build as such. The development build is in our source control system and not publicly available.
2) You should always backup your system before doing an upgrade. then you just restore your old files and database and you are "Rolled Back". There is no built in method for doing this in DNN.
3) Same as for doing upgrades. Just copy all the files in the file system and create a backup of the db. Then redeploy where you need. Make sure to update the PortalAlias table for the new URL.