Ok, thank you Benoit, worked like a charm.<br><br>Alberto<br><br><div><span class="gmail_quote">2007/1/11, Benoit Grégoire <<a href="mailto:bock@step.polymtl.ca">bock@step.polymtl.ca</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wednesday 10 January 2007 15:14, Gabe Sawhney wrote:<br>> I dunno how others do it, but I upgraded our auth server last week<br>> (from one that was even older than yours), this way:<br>><br>> - download from svn into a new folder, in the same apache virtual
<br>> server space (i.e. <a href="http://auth.wirelesstoronto.ca/newauth">auth.wirelesstoronto.ca/newauth</a>)<br>> - create a new postgres database called wifidog-new (or whatever)<br>> - pg_dump wifidog > wifidog.sql
<br>> - psql wifidog-new < wifidog.sql<br><br>That will prompty destroy all the Binary blobs (such as those in the Image<br>content type) on many versions of postgres.<br><br>Use the sql/backup_database.sh and sql/restore_database.sh scripts instead.
<br><br>> - run the install.php script as if it was a new install, and it<br>> upgrades the schema<br><br>Unless you missed a step, the wifidog-new is never used for anything, and not<br>modified bit the install script.
<br><br>> - bail on the install.php script after the schema upgrade ('cause<br>> otherwise it tries to create a new admin account)<br><br>It's more reliable to just go to the auth server home page to update the
<br>schema. The corresponding code in install.php will be deleted, and it may<br>not be safe.<br><br>> >From now on we'll be better about keeping it updated, so I'll just do<br>><br>> svn updates to the live site.
<br>><br>> If the process above seems bonkers to anyone, please let me know -- I<br>> promise to put the info on the wiki. <smile><br><br>Basically, the recommended process goes:<br>1-Read the Changelog (seriously)
<br>2-Use sql/backup_database.sh before the upgrade<br>3-Testing (optionnal, but recommended)<br>3.1-Checkout lastest SVN on a developement machine (not the same one as your<br>server, unless you really know what you are doing: you need to modify
<br>config.php to point to a different DB, and you cant's use the restore script<br>directly<br>3.2-Restore your live database on the development machine. Check if<br>everything seems in order (good tests are loging-in, viewing your most
<br>complicated portal and opening the Reusable content library). For a more<br>complete test (especially if you didn't upgrade in months), plug a gateway to<br>your development server and login, and try creating a new account.
<br>4-Run svn update on your live server<br>5-Go to your auth server home page to make sure the schema has been updated<br>(it may already have been by a random user accessing the auth server)<br>6-If the Changelog mentionned dependency changes (or if unsure), start the
<br>install script till the dependencies page.<br><br>--<br>Benoit Grégoire<br>Technologies Coeus inc.<br><br><br>_______________________________________________<br>WiFiDog mailing list<br><a href="mailto:WiFiDog@listes.ilesansfil.org">
WiFiDog@listes.ilesansfil.org</a><br><a href="http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog">http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog</a><br><br><br></blockquote></div><br>