Mercurial > kallithea
annotate docs/upgrade.rst @ 1237:f7bb54f8c20f
fixed archive names, added setup command to contributing docs.
author | Marcin Kuzminski <marcin@python-works.com> |
---|---|
date | Sat, 09 Apr 2011 20:15:18 +0200 |
parents | 93b980ebee55 |
children | bf263968da47 |
rev | line source |
---|---|
640 | 1 .. _upgrade: |
2 | |
3 Upgrade | |
4 ======= | |
5 | |
1091 | 6 Upgrading from Cheese Shop |
1095
3cdacd152b24
fixed sphinx build errors
Marcin Kuzminski <marcin@python-works.com>
parents:
1091
diff
changeset
|
7 -------------------------- |
640 | 8 |
1091 | 9 .. note:: |
1136
93b980ebee55
changes for release 1.1.5
Marcin Kuzminski <marcin@python-works.com>
parents:
1095
diff
changeset
|
10 Firstly, it is recommended that you **always** perform a database backup |
93b980ebee55
changes for release 1.1.5
Marcin Kuzminski <marcin@python-works.com>
parents:
1095
diff
changeset
|
11 before doing an upgrade. |
1091 | 12 |
13 The easiest way to upgrade ``rhodecode`` is to run:: | |
640 | 14 |
15 easy_install -U rhodecode | |
16 | |
17 Or:: | |
18 | |
19 pip install --upgrade rhodecode | |
20 | |
21 | |
1091 | 22 Then make sure you run the following command from the installation directory:: |
640 | 23 |
24 paster make-config RhodeCode production.ini | |
25 | |
1091 | 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 | |
1136
93b980ebee55
changes for release 1.1.5
Marcin Kuzminski <marcin@python-works.com>
parents:
1095
diff
changeset
|
28 to make a backup of your configuration file before hand and recheck the |
93b980ebee55
changes for release 1.1.5
Marcin Kuzminski <marcin@python-works.com>
parents:
1095
diff
changeset
|
29 content after the automerge. |
640 | 30 |
1071
bdc438fb4fe4
Fixes for release 1.1.4
Marcin Kuzminski <marcin@python-works.com>
parents:
845
diff
changeset
|
31 .. note:: |
bdc438fb4fe4
Fixes for release 1.1.4
Marcin Kuzminski <marcin@python-works.com>
parents:
845
diff
changeset
|
32 The next steps only apply to upgrading from non bugfix releases eg. from |
bdc438fb4fe4
Fixes for release 1.1.4
Marcin Kuzminski <marcin@python-works.com>
parents:
845
diff
changeset
|
33 any minor or major releases. Bugfix releases (eg. 1.1.2->1.1.3) will |
1091 | 34 not have any database schema changes or whoosh library updates. |
1071
bdc438fb4fe4
Fixes for release 1.1.4
Marcin Kuzminski <marcin@python-works.com>
parents:
845
diff
changeset
|
35 |
1136
93b980ebee55
changes for release 1.1.5
Marcin Kuzminski <marcin@python-works.com>
parents:
1095
diff
changeset
|
36 It is also recommended that you rebuild the whoosh index after upgrading since |
93b980ebee55
changes for release 1.1.5
Marcin Kuzminski <marcin@python-works.com>
parents:
1095
diff
changeset
|
37 the new whoosh version could introduce some incompatible index changes. |
845 | 38 |
39 | |
1091 | 40 The final step is to upgrade the database. To do this simply run:: |
845 | 41 |
1071
bdc438fb4fe4
Fixes for release 1.1.4
Marcin Kuzminski <marcin@python-works.com>
parents:
845
diff
changeset
|
42 paster upgrade-db production.ini |
845 | 43 |
1091 | 44 This will upgrade the schema and update some of the defaults in the database, |
1136
93b980ebee55
changes for release 1.1.5
Marcin Kuzminski <marcin@python-works.com>
parents:
1095
diff
changeset
|
45 and will always recheck the settings of the application, if there are no new |
93b980ebee55
changes for release 1.1.5
Marcin Kuzminski <marcin@python-works.com>
parents:
1095
diff
changeset
|
46 options that need to be set. |
845 | 47 |
640 | 48 |
49 .. _virtualenv: http://pypi.python.org/pypi/virtualenv | |
50 .. _python: http://www.python.org/ | |
51 .. _mercurial: http://mercurial.selenic.com/ | |
52 .. _celery: http://celeryproject.org/ | |
53 .. _rabbitmq: http://www.rabbitmq.com/ |