Show More
@@ -12,15 +12,23 b' 1.2.0 (**2010-12-18**)' | |||||
12 | news |
|
12 | news | |
13 | ++++ |
|
13 | ++++ | |
14 |
|
14 | |||
|
15 | - implemented #89 Can setup google analytics code from settings menu | |||
15 | - implemented #91 added nicer looking archive urls |
|
16 | - implemented #91 added nicer looking archive urls | |
16 | - implemented #44 into file browsing, and added follow branch option |
|
17 | - implemented #44 into file browsing, and added follow branch option | |
|
18 | - anonymous repository can be cloned without having to pass default:default | |||
|
19 | into clone url | |||
|
20 | - fixed #90 whoosh indexer can index chooses repositories passed in command | |||
|
21 | line | |||
17 |
|
22 | |||
18 | fixes |
|
23 | fixes | |
19 | ++++ |
|
24 | ++++ | |
20 |
|
25 | |||
21 | - fixed file browser bug, when switching into given form revision the url was |
|
26 | - fixed file browser bug, when switching into given form revision the url was | |
22 | not changing |
|
27 | not changing | |
23 | - fixed #92 |
|
28 | - fixed #92 whoosh indexer is more error proof | |
|
29 | - fixed large tooltips problems | |||
|
30 | - fixed propagation to error controller on simplehg and simplegit middlewares | |||
|
31 | ||||
24 |
|
32 | |||
25 | 1.1.0 (**2010-12-18**) |
|
33 | 1.1.0 (**2010-12-18**) | |
26 | ---------------------- |
|
34 | ---------------------- |
@@ -50,6 +50,31 b' You are ready to use rhodecode, to run i' | |||||
50 | anonymous, permissions settings. As well as edit more advanced options on |
|
50 | anonymous, permissions settings. As well as edit more advanced options on | |
51 | users and repositories |
|
51 | users and repositories | |
52 |
|
52 | |||
|
53 | Using RhodeCode with SSH | |||
|
54 | ------------------------ | |||
|
55 | ||||
|
56 | RhodeCode repository structures are kept in directories with the same name | |||
|
57 | as the project, when using repository groups, each group is a a subdirectory. | |||
|
58 | This will allow You to use ssh for accessing repositories quite easy. There | |||
|
59 | are some exceptions when using ssh for accessing repositories. | |||
|
60 | ||||
|
61 | You have to make sure that the webserver as well as the ssh users have unix | |||
|
62 | permission for directories. Secondly when using ssh rhodecode will not | |||
|
63 | authenticate those requests and permissions set by the web interface will not | |||
|
64 | work on the repositories accessed via ssh. There is a solution to this to use | |||
|
65 | auth hooks, that connects to rhodecode db, and runs check functions for | |||
|
66 | permissions. | |||
|
67 | ||||
|
68 | TODO: post more info on this ! | |||
|
69 | ||||
|
70 | if Your main directory (the same as set in RhodeCode settings) is set to | |||
|
71 | for example `\home\hg` and repository You are using is `rhodecode` | |||
|
72 | ||||
|
73 | The command runned should look like this:: | |||
|
74 | hg clone ssh://user@server.com/home/hg/rhodecode | |||
|
75 | ||||
|
76 | Using external tools such as mercurial server or using ssh key based auth is | |||
|
77 | fully supported. | |||
53 |
|
78 | |||
54 | Setting up Whoosh full text search |
|
79 | Setting up Whoosh full text search | |
55 | ---------------------------------- |
|
80 | ---------------------------------- |
General Comments 0
You need to be logged in to leave comments.
Login now