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 |
||
11 |
Then configure and build IVLE. New configuration options may sometimes |
|
12 |
be added, so the configuration questions should be watched closely. |
|
13 |
||
14 |
./setup.py listmake |
|
15 |
./setup.py config |
|
16 |
./setup.py build |
|
17 |
||
18 |
Note that this will not perform a full rebuild of the template jail - |
|
19 |
only the IVLE files inside the jail will be updated. To force a full |
|
20 |
jail rebuild, give the build command the -j option. |
|
21 |
||
22 |
Now comes the time to block external access to IVLE. Stopping Apache |
|
23 |
on each server in the cluster and killing any remaining python-console |
|
24 |
processes is highly recommended. |
|
25 |
||
26 |
You should then run any outstanding database migrations. A note of the |
|
27 |
latest applied migration should probably be kept somewhere to avoid |
|
28 |
running the same one twice. This command must be run once for each. |
|
29 |
||
30 |
sudo -u postgres ivle < userdb/migrations/YYYYMMDD-NN.sql |
|
31 |
||
32 |
Now we can install the new version: |
|
33 |
||
34 |
./setup.py install |
|
35 |
||
36 |
... and remake the user jails, as this will occasionally be needed: |
|
37 |
||
38 |
./remakeuser.py --all --verbose |
|
39 |
||
40 |
Restart the usrmgt-server and all Apaches, reenable external access, |
|
41 |
check that everything works, and you're done! |