blob: 4e6ea19c1b413c261ade110ece636441cde5da6c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
.. _upgrade:
=======
Upgrade
=======
Upgrading from PyPI (aka "Cheeseshop")
---------------------------------------
.. note::
Firstly, it is recommended that you **always** perform a database and
configuration backup before doing an upgrade.
(These directions will use '{version}' to note that this is the version of
Rhodecode that these files were used with. If backing up your RhodeCode
instance from version 1.3.6 to 1.4.0, the ``production.ini`` file would be
backed up to ``production.ini.1-3-6``.)
If using a sqlite database, stop the Rhodecode process/daemon/service, and
then make a copy of the database file::
service rhodecode stop
cp rhodecode.db rhodecode.db.{version}
Back up your configuration file::
cp production.ini production.ini.{version}
Ensure that you are using the Python Virtual Environment that you'd originally
installed Rhodecode in::
pip freeze
will list all packages installed in the current environment. If Rhodecode
isn't listed, change virtual environments to your venv location::
source /opt/rhodecode-venv/bin/activate
Once you have verified the environment you can upgrade ``Rhodecode`` with::
easy_install -U rhodecode
Or::
pip install --upgrade rhodecode
Then run the following command from the installation directory::
paster make-config RhodeCode production.ini
This will display any changes made by the new version of RhodeCode to your
current configuration. It will try to perform an automerge. It's recommended
that you re-check the content after the automerge.
.. note::
Please always make sure your .ini files are up to date. Often errors are
caused by missing params added in new versions.
It is also recommended that you rebuild the whoosh index after upgrading since
the new whoosh version could introduce some incompatible index changes. Please
Read the changelog to see if there were any changes to whoosh.
The final step is to upgrade the database. To do this simply run::
paster upgrade-db production.ini
This will upgrade the schema and update some of the defaults in the database,
and will always recheck the settings of the application, if there are no new
options that need to be set.
You may find it helpful to clear out your log file so that new errors are
readily apparent::
echo > rhodecode.log
Once that is complete, you may now start your upgraded Rhodecode Instance::
service rhodecode start
Or::
paster serve /var/www/rhodecode/production.ini
.. note::
If you're using Celery, make sure you restart all instances of it after
upgrade.
.. _virtualenv: http://pypi.python.org/pypi/virtualenv
.. _python: http://www.python.org/
.. _mercurial: http://mercurial.selenic.com/
.. _celery: http://celeryproject.org/
.. _rabbitmq: http://www.rabbitmq.com/
|
