| 1 |
blueness 11/02/22 16:22:08 |
| 2 |
|
| 3 |
Modified: postinstall-en.txt |
| 4 |
Log: |
| 5 |
Version bumps. |
| 6 |
|
| 7 |
(Portage version: 2.1.9.25/cvs/Linux x86_64) |
| 8 |
|
| 9 |
Revision Changes Path |
| 10 |
1.3 www-apps/moodle/files/postinstall-en.txt |
| 11 |
|
| 12 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/www-apps/moodle/files/postinstall-en.txt?rev=1.3&view=markup |
| 13 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/www-apps/moodle/files/postinstall-en.txt?rev=1.3&content-type=text/plain |
| 14 |
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/www-apps/moodle/files/postinstall-en.txt?r1=1.2&r2=1.3 |
| 15 |
|
| 16 |
Index: postinstall-en.txt |
| 17 |
=================================================================== |
| 18 |
RCS file: /var/cvsroot/gentoo-x86/www-apps/moodle/files/postinstall-en.txt,v |
| 19 |
retrieving revision 1.2 |
| 20 |
retrieving revision 1.3 |
| 21 |
diff -u -r1.2 -r1.3 |
| 22 |
--- postinstall-en.txt 13 Aug 2010 19:04:29 -0000 1.2 |
| 23 |
+++ postinstall-en.txt 22 Feb 2011 16:22:08 -0000 1.3 |
| 24 |
@@ -98,8 +98,51 @@ |
| 25 |
|
| 26 |
UPGRADES |
| 27 |
|
| 28 |
- TODO - When the next release is out, I will fill this |
| 29 |
- section in. |
| 30 |
+0 Before any upgade you should backup your database in case you have |
| 31 |
+ to roll back. The moodle dirroot directory ($CFG->dirroot in the |
| 32 |
+ config.php file) isn't as critical since you can always reinstall |
| 33 |
+ that with web-apps. The moodle data root ($CFG->dataroot in config.php), |
| 34 |
+ where files are uploaded, will not be touched. But the upgrade will |
| 35 |
+ probably change your db schema, and the new format may not be backward |
| 36 |
+ compatible. For mysql use |
| 37 |
+ |
| 38 |
+ mysqldump -u moodle_user -p -C -Q -e --create-options moodle_db > moodle-backup.sql |
| 39 |
+ |
| 40 |
+ or for postgresql use |
| 41 |
+ |
| 42 |
+ su - postgres |
| 43 |
+ pg_dump moodle_db > moodle-backup.sql |
| 44 |
+ |
| 45 |
+ If you have to fall back, you can do so using |
| 46 |
+ |
| 47 |
+ mysql -p -u moodle_user moodle_db < moodle-backup.sql |
| 48 |
+ |
| 49 |
+ or |
| 50 |
+ |
| 51 |
+ su - postgres |
| 52 |
+ psql moodle_db < moodle-backup.sql |
| 53 |
+ |
| 54 |
+ TEST THIS! PRACTICE THIS! Make sure it will work for you if you |
| 55 |
+ have to fall back. |
| 56 |
+ |
| 57 |
+1 Emerge the new moodle ebuild. Be prepared to add USE flags for |
| 58 |
+ php and re-emerge it since upgrades may require new functionality |
| 59 |
+ from php. Remember to restart apache after re-emerging php! |
| 60 |
+ |
| 61 |
+2 If the ebuild didn't do it for you, update using |
| 62 |
+ |
| 63 |
+ webapp-config -d moodle -U moodle X.Y.Z |
| 64 |
+ |
| 65 |
+3 Aim your browser to the URL in the config.php file defined |
| 66 |
+ by $CFG->wwwroot. You will get a message that you are about |
| 67 |
+ to automatically upgrade your server and cannot go back. |
| 68 |
+ This is why you backed up your db in step 1. You can go back |
| 69 |
+ if you use webapp-config to install the older version AND |
| 70 |
+ drop the new db and restart the old one. You did practice |
| 71 |
+ restoring, right? |
| 72 |
+ |
| 73 |
+4 Click "Continue" and follow through with the upgrade. |
| 74 |
+ |
| 75 |
|
| 76 |
================================================================= |
| 77 |
|
| 78 |
@@ -174,3 +217,4 @@ |
| 79 |
LDAP or CAS ldap |
| 80 |
External database odbc |
| 81 |
RADIUS radius |
| 82 |
+ |
Archives