Upgrade instructions for the 20090524 release

[Robert Kaye]

Please follow these steps to upgrade your installation:

0. Make sure that all packets have been applied to current database.  
You should see an error like this:

     This replication packet matches schema sequence #11, but the  
database is currently at #10
     You must upgrade your database in order to apply this replication  
packet

1. Check out the new code base from subversion and place it in the  
same top level
   directory as the current codebase:

     svn co http://svn.musicbrainz.org/mb_server/branches/RELEASE_20090524-BRANCH 
  mb_server-20090524

3. Configure your new codebase and copy new config files:

     cd mb_server-20090524/cgi-bin
     cp DBDefs.pm.default DBDefs.pm

4. Edit cgi-bin/DBDefs.pm and copy over the appropriate configuration  
items from the old codebase:

   a. DBDefs.pm needs DB config settings changed. Also make sure that  
REPLICATION_TYPE is
      set to RT_SLAVE. Set the WEB_SERVER and RDF_SERVER settings to  
match your old
      configuration. Then review the file to make sure nothing else  
needs changing.
      It might be useful to diff your old config file against the new  
one to make sure
      you handled everything.

   Test your configuration by doing:

   cd <to admin dir>
   ./psql READWRITE

   That should get you to your database server shell if everything is  
configured right. \q to exit.

5. In admin/apache you will want to create startup.pl,  
vh_mb_backend.conf by
copying them from the .default files and adjusting all the sections
marked with TODO. Include startup.pl and vh_mb_backend.conf in your
apache configuration if you actually run the MusicBrainz site on your
system. If you have a database only install, you can skip this step.

5. Turn off cron jobs that might affect the server update.

6. Run the automatic database upgrade script:

   cd <top level mb_server dir>
   ./upgrade.sh

   This should run for quite some time as it updates the database to  
be ready for the new features.

7. Test the update by loading more replication changes:

   cd replication
   ./LoadReplicationChanges

   You should see your database catch up to the latest replication  
sequence.

8. Turn cron jobs back on.

9. You're done!

Please post any questions/issues you might have here.

Thanks!
--

--ruaok      A village in Texas has its idiot back!

Robert Kaye     --     rob@...     --    http://mayhem-chaos.net


_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed