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
100
101
102
103
104
105
106
107
|
.. _general:
=======================
General RhodeCode usage
=======================
Repository deleting
-------------------
Currently when admin/owner deletes a repository, RhodeCode does not physically
delete a repository from filesystem, it renames it in a special way so it's
not possible to push,clone or access repository. It's worth a notice that,
even if someone will be given administrative access to RhodeCode and will
delete a repository You can easy restore such action by restoring `rm__<date>`
from the repository name, and internal repository storage (.hg/.git)
Follow current branch in file view
----------------------------------
In file view when this checkbox is checked the << and >> arrows will jump
to changesets within the same branch currently viewing. So for example
if someone is viewing files at 'beta' branch and marks `follow current branch`
checkbox the << and >> buttons will only show him revisions for 'beta' branch
Compare view from changelog
---------------------------
Checkboxes in compare view allow users to view combined compare view. You can
only show the range between the first and last checkbox (no cherry pick).
Clicking more than one checkbox will activate a link in top saying
`Show selected changes <from-rev> -> <to-rev>` clicking this will bring
compare view
Compare view is also available from the journal on pushes having more than
one changeset
Non changeable repository urls
------------------------------
Due to complicated nature of repository grouping, often urls of repositories
can change.
example::
#before
http://server.com/repo_name
# after insertion to test_group group the url will be
http://server.com/test_group/repo_name
This can be an issue for build systems and any other hardcoded scripts, moving
repository to a group leads to a need for changing external systems. To
overcome this RhodeCode introduces a non changable replacement url. It's
simply an repository ID prefixed with `_` above urls are also accessible as::
http://server.com/_<ID>
Since ID are always the same moving the repository will not affect such url.
the _<ID> syntax can be used anywhere in the system so urls with repo_name
for changelogs, files and other can be exchanged with _<ID> syntax.
Mailing
-------
When administrator will fill up the mailing settings in .ini files
RhodeCode will send mails on user registration, or when RhodeCode errors occur
on errors the mails will have a detailed traceback of error.
Mails are also sent for code comments. If someone comments on a changeset
mail is sent to all participants, the person who commited the changeset
(if present in RhodeCode), and to all people mentioned with @mention system.
Trending source files
---------------------
Trending source files are calculated based on pre defined dict of known
types and extensions. If You miss some extension or Would like to scan some
custom files it's possible to add new types in `LANGUAGES_EXTENSIONS_MAP` dict
located in `/rhodecode/lib/celerylib/tasks.py`
Cloning remote repositories
---------------------------
RhodeCode has an ability to clone remote repos from given remote locations.
Currently it support following options:
- hg -> hg clone
- svn -> hg clone
- git -> git clone
.. note::
- *`svn -> hg` cloning requires `hgsubversion` library to be installed.*
If you need to clone repositories that are protected via basic auth, you
might pass the url with stored credentials inside eg.
`http://user:passw@remote.server/repo, RhodeCode will try to login and clone
using given credentials. Please take a note that they will be stored as
plaintext inside the database. RhodeCode will remove auth info when showing the
clone url in summary page.
|
