##// END OF EJS Templates
upstream » kallithea
RSS

Clone from https://kallithea-scm.org/repos/kallithea

updated contributing docs
marcink -
r3993:b53cef6f default
parent child Browse files
Show More
Show file before | Show file after | Hide comments
@@ -10,13 +10,15 b' greatly appreciated!'
10 Could I request that you make your source contributions by first forking the
10 Could I request that you make your source contributions by first forking the
11 RhodeCode repository on bitbucket_
11 RhodeCode repository on bitbucket_
12 https://bitbucket.org/marcinkuzminski/rhodecode and then make your changes to
12 https://bitbucket.org/marcinkuzminski/rhodecode and then make your changes to
13 your forked repository. Please post all fixes into **BETA** branch since your
13 your forked repository. Please post all fixes into **dev** bookmark since your
14 fix might be already fixed there and i try to merge all fixes from beta into
14 change might be already fixed there and i try to merge all fixes from dev into
15 stable, and not the other way. Finally, when you are finished making a change,
15 stable, and not the other way. Finally, when you are finished with your changes,
16 please send me a pull request.
16 please send me a pull request.
17
17
18 To run RhodeCode in a development version you always need to install the latest
18 To run RhodeCode in a development version you always need to install the latest
19 required libs from `requires.txt` file.
19 required libs. Simply clone rhodecode and switch to beta branch::
20
21 hg clone -u dev https://secure.rhodecode.org/rhodecode
20
22
21 after downloading/pulling RhodeCode make sure you run::
23 after downloading/pulling RhodeCode make sure you run::
22
24
@@ -25,10 +27,23 b' after downloading/pulling RhodeCode make'
25 command to install/verify all required packages, and prepare development
27 command to install/verify all required packages, and prepare development
26 enviroment.
28 enviroment.
27
29
30 There are two files in the directory production.ini and developement.ini copy
31 the `development.ini` file as rc.ini (which is excluded from version controll)
32 and put all your changes like db connection or server port in there.
28
33
29 After finishing your changes make sure all tests passes ok. You can run
34 After finishing your changes make sure all tests passes ok. You can run
30 the testsuite running ``nosetest`` from the project root, or if you use tox
35 the testsuite running ``nosetest`` from the project root, or if you use tox
31 run tox for python2.5-2.7 with multiple database test.
36 run tox for python2.5-2.7 with multiple database test. When using `nosetests`
37 test.ini file is used and by default it uses sqlite for tests, edit this file
38 to change your testing enviroment.
39
40
41 There's a special set of tests for push/pull operations, you can runn them using::
42
43 paster serve test.ini --pid-file=test.pid --daemon
44 RC_WHOOSH_TEST_DISABLE=1 RC_NO_TMP_PATH=1 nosetests -x rhodecode/tests/other/test_vcs_operations.py
45 kill -9 $(cat test.pid)
46
32
47
33 | Thank you for any contributions!
48 | Thank you for any contributions!
34 | Marcin
49 | Marcin
General Comments 0
You need to be logged in to leave comments. Login now