Zikula Community

• MarcPare
  
  

  • Rank: Softmore
  • Registered: Dec 10, 2003
  • Last visit: May 12, 2010
  • Posts: 299

  Posted: Oct 29, 2011 - 05:29 AM

  I just wanted to ask what do you normally do before migrating a site to a different version. Let's say a Zikula v.1.2.X site being migrated Zikula v.1.3.X ?
  
  * Do you test it on your own LAMP server or do you test it on your hosted server but on an account reserved to testing?
  * If you test it on your own LAMP, do you have a dedicated box for this? or do you use your normal day-to-day box and just happen to have the LAMP installed on it?
  
  I think this would help those of us who are new to running CMS sites know how to properly test migrating/upgrading sites that we really would not like to mess up on a live migrate/upgrade.
  
  Thanks for any input.
  
  Marc

  • 
  •  
• pheski
  
  

  • Rank: Expert
  • Registered: Feb 27, 2005
  • Last visit: Apr 18, 2010
  • Posts: 1577

  Posted: Oct 29, 2011 - 05:58 AM

  My answer is yes.
  
  I don't actually use LAMP, but I have a localhost install of MySQL and PHP and generally test an upgrade there on generic installs first. It's quick and easy.
  
  Then I like to make a mirror of my hosted site on my localhost and try the upgrade there. (Though it is impossible to make my localhost perfectly mirror the hosted environment, of course.)
  
  If that works, then I do the upgrade of the production site.
  
  I have sometimes duplicated my hosted site on the host in order to try the upgrade there. Usually not. But my sites tend to be relatively low key and in my hosted environment I can ask the host to replace the old setup from the previous night back-up.
  
  HTH
  
  Peter
  
  --
  Peace
  ______________________________________
  The commonest cause of problems is solutions.

  • 
  •  
• slam
  
  

  • Rank: Team Member
  • Registered: May 03, 2004
  • Last visit: May 31, 2010
  • Posts: 511

  Posted: Oct 29, 2011 - 02:44 PM

  Best practice:
  
  1) Backup files and database of your live site.
  2) Test this backup by playing it back into a sub directory at the same server, with a new database or a different table prefix.
  3) Run your upgrade tests on this very duplicate.
  4) If the upgrade satisfies you, simply replace the files in your web root.
  5) Remove the old database/tables with old prefix.
  
  It makes no sense to test on XAMP, LAMP or localhost, except you are a server admin pro and run exactly the same system on the web server and your workstation (which is most likely not the case).
  
  Greetings,
  Chris
  
  
  
  Edited by slam on Oct 30, 2011 - 03:44 AM.
  
  --
  an operating system must operate
  development is life
  my repo

  • 
  •  
• espaan
  
  

  • Rank: Developer
  • Registered: Aug 23, 2003
  • Last visit: May 31, 2010
  • Posts: 1428

  Posted: Oct 29, 2011 - 04:58 PM

  Yes, always backup everything (do a cleanup of DB tables first and a clearing of caches (render/theme) i you have them enabled).
  
  For a major upgrade of 12x to 13x I always like to test the whole site locally (I use MAMP on the mac).
  Some modules might not be available any more and you need a new one or the theme needs adjustment. I like to test that locally or in a subdir on the webhost with a separate DB. Locally I can test a bit faster and easier than on a webhost. But that is of course up to you
  
  --
  campertoday.nl, Module development, Dutch Zikula Community

  • 
  •  
•  
•  

Users on-line

• 0 users

This list is based on users active over the last 60 minutes.