doc/6 now has anchors
This commit is contained in:
parent
6f740339e4
commit
8d382a6d25
|
@ -43,6 +43,8 @@ are using your shell access -- instead of running via
|
|||
`/some/path/gl-auth-command <your_username>` it is just going to bash and
|
||||
working from there!]
|
||||
|
||||
<a name="basic"></a>
|
||||
|
||||
### basic ssh troubleshooting
|
||||
|
||||
[glb]: http://sitaramc.github.com/0-installing/9-gitolite-basics.html#IMPORTANT_overview_of_ssh
|
||||
|
@ -182,6 +184,8 @@ you had command line access to the server *before* you were added as a
|
|||
gitolite user. If you send that same key to your gitolite admin to include in
|
||||
the admin repo, it won't work. For reasons why, see below.
|
||||
|
||||
<a name="details"></a>
|
||||
|
||||
### details
|
||||
|
||||
Here's how it all hangs together.
|
||||
|
@ -348,6 +352,8 @@ that should have enough info to get you going (but it helps to know ssh well):
|
|||
|
||||
That should do it.
|
||||
|
||||
<a name="complex"></a>
|
||||
|
||||
### more complex ssh setups
|
||||
|
||||
What do you need to know in order to create more complex ssh setups (for
|
||||
|
@ -373,6 +379,8 @@ instance if you have *two* gitolite servers you are administering)?
|
|||
* now access one server's repos as `gitolite:reponame.git` and the other
|
||||
server's repos as `gitolite2:reponame.git`.
|
||||
|
||||
<a name="shell"></a>
|
||||
|
||||
### giving shell access to gitolite users
|
||||
|
||||
We've managed (thanks to an idea from Jesse Keating) to make it possible for a
|
||||
|
|
Loading…
Reference in a new issue