diff options
| author | Étienne Loks <etienne.loks@peacefrogs.net> | 2011-06-23 12:29:44 +0200 |
|---|---|---|
| committer | Étienne Loks <etienne.loks@peacefrogs.net> | 2011-06-23 12:29:44 +0200 |
| commit | cff1e15b90c729264912349a92b64449a14755a3 (patch) | |
| tree | a7831ac6542f4e155aca0efc17fe00d7fbb610b9 | |
| parent | 1bf1efd68f0779cf6ca9f65d5498d10a1688db11 (diff) | |
| download | Chimère-cff1e15b90c729264912349a92b64449a14755a3.tar.bz2 Chimère-cff1e15b90c729264912349a92b64449a14755a3.zip | |
Documentation updatev1.1.2
| -rw-r--r-- | docs/en/UPGRADE.t2t | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/en/UPGRADE.t2t b/docs/en/UPGRADE.t2t index e57faad..7d248ee 100644 --- a/docs/en/UPGRADE.t2t +++ b/docs/en/UPGRADE.t2t @@ -110,6 +110,9 @@ to backup your database. You can also make a copy of your current database into a new database and make the new installation to this new database. +The gdal binding for python is necessary to run the upgrade scripts (available +in the python-gdal package in Debian). + If you run the migration scripts in a production environnement stop the old instance of Chimère before executing the migration script. Perhaps prepare the web server to point to the new installation before doing the database upgrade |