~azzar1/unity/add-show-desktop-key

931 by wagrant
doc: Add documentation on upgrading to a new SVN revision.
1
Upgrade Procedure for IVLE
2
==========================
3
4
Upgrading to a new revision of IVLE SVN is generally fairly painless,
5
but there are several steps involved.
6
7
Firstly, in the IVLE checkout, bring your codebase up to date:
8
9
  svn update
10
965 by apeel
Added paragraph on checking the svn logs to see whether modifications have
11
Review the IVLE code changes. The current installed IVLE version can
12
be found in /opt/ivle/version/ivle-revision.txt. 
13
eg. run 'svn log -v --limit 20' to get the last 20 checking messages.
14
Look to see whether there have been any changes to the jails or
15
database tables.
16
931 by wagrant
doc: Add documentation on upgrading to a new SVN revision.
17
Then configure and build IVLE. New configuration options may sometimes
18
be added, so the configuration questions should be watched closely.
19
20
  ./setup.py config
965 by apeel
Added paragraph on checking the svn logs to see whether modifications have
21
  sudo ./setup.py build
931 by wagrant
doc: Add documentation on upgrading to a new SVN revision.
22
23
Note that this will not perform a full rebuild of the template jail -
24
only the IVLE files inside the jail will be updated. To force a full
25
jail rebuild, give the build command the -j option.
26
27
Now comes the time to block external access to IVLE. Stopping Apache
28
on each server in the cluster and killing any remaining python-console
29
processes is highly recommended.
30
31
You should then run any outstanding database migrations. A note of the
32
latest applied migration should probably be kept somewhere to avoid
33
running the same one twice. This command must be run once for each.
34
35
  sudo -u postgres ivle < userdb/migrations/YYYYMMDD-NN.sql
36
37
Now we can install the new version:
38
965 by apeel
Added paragraph on checking the svn logs to see whether modifications have
39
  sudo ./setup.py install
931 by wagrant
doc: Add documentation on upgrading to a new SVN revision.
40
41
... and remake the user jails, as this will occasionally be needed:
42
1079 by William Grant
Merge setup-refactor branch. This completely breaks existing installations;
43
  ivle-remakeuser --all --verbose
931 by wagrant
doc: Add documentation on upgrading to a new SVN revision.
44
45
Restart the usrmgt-server and all Apaches, reenable external access,
46
check that everything works, and you're done!