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