Upgrade » History » Version 4
Anthony Mallet, 2014-01-09 11:51
1 | 2 | Anthony Mallet | h1. Upgrade procedure |
---|---|---|---|
2 | 1 | Anthony Mallet | |
3 | Pull updates from the local repository (<code>laas</code> branch). |
||
4 | <pre> |
||
5 | # su - redmine |
||
6 | 4 | Anthony Mallet | % cd src/laas (or src/openrobots) |
7 | % git pull |
||
8 | 1 | Anthony Mallet | </pre> |
9 | |||
10 | Install new gems, if any. |
||
11 | <pre> |
||
12 | 4 | Anthony Mallet | % bundle install |
13 | 1 | Anthony Mallet | </pre> |
14 | This may fail, because of conflicting packages. <code>bundle update</code> should fix that. |
||
15 | |||
16 | Then, migrate database (might be a no-op). |
||
17 | <pre> |
||
18 | 4 | Anthony Mallet | % rake db:migrate RAILS_ENV=production |
19 | % rake redmine:plugins:migrate RAILS_ENV=production |
||
20 | 1 | Anthony Mallet | </pre> |
21 | |||
22 | 4 | Anthony Mallet | It may be desirable to recompile apache passenger module, if <code>bundle install</code> upgraded it. This is however optional: the old version will still work without any action, if the old gem is not cleaned (see below). |
23 | <pre> |
||
24 | % passenger-install-apache2-module |
||
25 | % vi /etc/httpd/conf.d/laas.conf (or openrobots.conf) for the new passenger module path |
||
26 | </pre> |
||
27 | |||
28 | It may also be desirable to clean old gems |
||
29 | <pre> |
||
30 | % bundle clean |
||
31 | </pre> |
||
32 | |||
33 | 1 | Anthony Mallet | Restart passenger. |
34 | <pre> |
||
35 | 4 | Anthony Mallet | % touch tmp/restart.txt |
36 | 1 | Anthony Mallet | </pre> |