On Aug 31, 2012, at 12:17 01, ICR Programs wrote:

> for those of us who aren't power users, could you please explain a bit about 
> the preferred method of updating from vs 2.1.5 on the CentOS (Broadcast 
> Appliance) system?

Assuming that you have Internet access, the process is largely automatic.  The 
system will notify you via a popup that an update is ready.  The procedure is:

1) Make a database backup (in RDAdmin->BackupDatabase).  Don't skip this step!

2) Select one system to do the initial update and apply any schema changes 
necessary.  You want to complete the update on this one system before doing any 
others!

3) Close any active Rivendell modules.

3) If the update popup is still visible, click the 'View Updates' button, 
otherwise run 'Software Updater' on the 'System' menu.  The system will prompt 
for the administrator (root) password.

4) Click the 'Apply Updates' button.

5) Once the initial system has finished, go ahead and update all the others, 
using the same procedure (steps 3 and 4).  It's strongly recommended that all 
the hosts using a common server use the same Rivendell version.  Mixing 
different versions together can have side effects ranging from unnoticable to 
catastrophic (database corruption due to schema skew).  You did do a database 
backup before starting this, right?

That's all there is to it.

Cheers!


|-------------------------------------------------------------------------|
| Frederick F. Gleason, Jr. |               Chief Developer               |
|                           |               Paravel Systems               |
|-------------------------------------------------------------------------|
|          A room without books is like a body without a soul.            |
|                                         -- Cicero                       |
|-------------------------------------------------------------------------|

_______________________________________________
Rivendell-dev mailing list
[email protected]
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev

Reply via email to