##// END OF EJS Templates
added info to ugprade docs to restart celery
marcink -
r2115:8dfb265f beta
parent child Browse files
Show More
@@ -1,55 +1,58 b''
1 .. _upgrade:
1 .. _upgrade:
2
2
3 =======
3 =======
4 Upgrade
4 Upgrade
5 =======
5 =======
6
6
7 Upgrading from Cheese Shop
7 Upgrading from Cheese Shop
8 --------------------------
8 --------------------------
9
9
10 .. note::
10 .. note::
11 Firstly, it is recommended that you **always** perform a database backup
11 Firstly, it is recommended that you **always** perform a database backup
12 before doing an upgrade.
12 before doing an upgrade.
13
13
14 The easiest way to upgrade ``rhodecode`` is to run::
14 The easiest way to upgrade ``rhodecode`` is to run::
15
15
16 easy_install -U rhodecode
16 easy_install -U rhodecode
17
17
18 Or::
18 Or::
19
19
20 pip install --upgrade rhodecode
20 pip install --upgrade rhodecode
21
21
22
22
23 Then make sure you run the following command from the installation directory::
23 Then make sure you run the following command from the installation directory::
24
24
25 paster make-config RhodeCode production.ini
25 paster make-config RhodeCode production.ini
26
26
27 This will display any changes made by the new version of RhodeCode to your
27 This will display any changes made by the new version of RhodeCode to your
28 current configuration. It will try to perform an automerge. It's always better
28 current configuration. It will try to perform an automerge. It's always better
29 to make a backup of your configuration file before hand and re check the
29 to make a backup of your configuration file before hand and re check the
30 content after the automerge.
30 content after the automerge.
31
31
32 .. note::
32 .. note::
33 Please always make sure your .ini files are up to date. Often errors are
33 Please always make sure your .ini files are up to date. Often errors are
34 caused by missing params added in new versions.
34 caused by missing params added in new versions.
35
35
36
36
37 It is also recommended that you rebuild the whoosh index after upgrading since
37 It is also recommended that you rebuild the whoosh index after upgrading since
38 the new whoosh version could introduce some incompatible index changes. Please
38 the new whoosh version could introduce some incompatible index changes. Please
39 Read the changelog to see if there were any changes to whoosh.
39 Read the changelog to see if there were any changes to whoosh.
40
40
41
41
42 The final step is to upgrade the database. To do this simply run::
42 The final step is to upgrade the database. To do this simply run::
43
43
44 paster upgrade-db production.ini
44 paster upgrade-db production.ini
45
45
46 This will upgrade the schema and update some of the defaults in the database,
46 This will upgrade the schema and update some of the defaults in the database,
47 and will always recheck the settings of the application, if there are no new
47 and will always recheck the settings of the application, if there are no new
48 options that need to be set.
48 options that need to be set.
49
49
50 .. note::
51 If you're using Celery, make sure you restart all instances of it after
52 upgrade.
50
53
51 .. _virtualenv: http://pypi.python.org/pypi/virtualenv
54 .. _virtualenv: http://pypi.python.org/pypi/virtualenv
52 .. _python: http://www.python.org/
55 .. _python: http://www.python.org/
53 .. _mercurial: http://mercurial.selenic.com/
56 .. _mercurial: http://mercurial.selenic.com/
54 .. _celery: http://celeryproject.org/
57 .. _celery: http://celeryproject.org/
55 .. _rabbitmq: http://www.rabbitmq.com/ No newline at end of file
58 .. _rabbitmq: http://www.rabbitmq.com/
General Comments 0
You need to be logged in to leave comments. Login now