@@ -5,29 +5,32 @@ Contributing to RhodeCode
If you would like to contribute to RhodeCode, please contact me, any help is
greatly appreciated!
Could I request that you make your source contributions by first forking the
RhodeCode repository on bitbucket_
https://bitbucket.org/marcinkuzminski/rhodecode and then make your changes to
your forked repository. Please post all fixes into **BETA** branch since your
fix might be already fixed there and i try to merge all fixes from beta into
stable, and not the other way. Finally, when you are finished making a change,
please send me a pull request.
To run RhodeCode in a development version you always need to install the tip
version of RhodeCode and the VCS library.
To run RhodeCode in a development version you always need to install the latest
required libs from `requires.txt` file.
after downloading RhodeCode make sure you run::
after downloading/pulling RhodeCode make sure you run::
python setup.py develop
command to install all required packages, and prepare development enviroment
command to install/verify all required packages, and prepare development
enviroment.
After finishing your changes make sure all tests passes ok. You can run
the testsuite running nosetest from the project root.
| Thank you for any contributions!
| Marcin
.. _bitbucket: http://bitbucket.org/
@@ -16,29 +16,29 @@ The easiest way to upgrade ``rhodecode``
Or::
pip install --upgrade rhodecode
Then make sure you 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 always better
to make a backup of your configuration file before hand and recheck the
to make a backup of your configuration file before hand and re check the
content after the automerge.
.. note::
Please always make sure your .ini files are upto date. Often errors are
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
Status change: