(more ssh documentation shenanigans)
This commit is contained in:
parent
c1bd3ca69c
commit
6c48647c15
|
@ -36,6 +36,10 @@ code, and documentation.**
|
||||||
|
|
||||||
Other resources:
|
Other resources:
|
||||||
|
|
||||||
|
* people who think this is too hard should take a look at
|
||||||
|
[doc/7-install-transcript.mkd][doc7] to **see how simple it *actually*
|
||||||
|
is**.
|
||||||
|
|
||||||
* I **strongly** recommend reading [doc/9-gitolite-and-ssh.mkd][doc9gas],
|
* I **strongly** recommend reading [doc/9-gitolite-and-ssh.mkd][doc9gas],
|
||||||
which is a very detailed look at how gitolite uses ssh's features on the
|
which is a very detailed look at how gitolite uses ssh's features on the
|
||||||
server side. Most people don't know ssh as well as they *think* they do;
|
server side. Most people don't know ssh as well as they *think* they do;
|
||||||
|
@ -461,3 +465,4 @@ bigger problems than gitolite install not working!)]
|
||||||
[fc]: http://github.com/sitaramc/gitolite/blob/pu/doc/0-INSTALL.mkd#from_client_method_install_from_the_client_to_the_server
|
[fc]: http://github.com/sitaramc/gitolite/blob/pu/doc/0-INSTALL.mkd#from_client_method_install_from_the_client_to_the_server
|
||||||
[urls]: http://github.com/sitaramc/gitolite/blob/pu/doc/0-INSTALL.mkd#URLs_for_gitolite_managed_repos
|
[urls]: http://github.com/sitaramc/gitolite/blob/pu/doc/0-INSTALL.mkd#URLs_for_gitolite_managed_repos
|
||||||
[repout]: http://github.com/sitaramc/gitolite/blob/pu/doc/report-output.mkd
|
[repout]: http://github.com/sitaramc/gitolite/blob/pu/doc/report-output.mkd
|
||||||
|
[doc7]: http://github.com/sitaramc/gitolite/blob/pu/doc/7-install-transcript.mkd
|
||||||
|
|
|
@ -1,10 +1,30 @@
|
||||||
# gitolite install transcript
|
# gitolite install transcript
|
||||||
|
|
||||||
|
In this document:
|
||||||
|
|
||||||
|
* <a href="#about_this_document">about this document</a>
|
||||||
|
* <a href="#create_userids_on_server_and_client_optional_">create userids on server and client (optional)</a>
|
||||||
|
* <a href="#get_pubkey_access_from_client_to_server">get pubkey access from client to server</a>
|
||||||
|
* <a href="#get_gitolite_source">get gitolite source</a>
|
||||||
|
* <a href="#install_gitolite">install gitolite</a>
|
||||||
|
* <a href="#VERY_IMPORTANT_">VERY IMPORTANT...</a>
|
||||||
|
* <a href="#examine_what_you_have">examine what you have</a>
|
||||||
|
* <a href="#emergency_password_access">emergency password access</a>
|
||||||
|
|
||||||
|
----
|
||||||
|
|
||||||
|
<a name="about_this_document"></a>
|
||||||
|
|
||||||
|
### about this document
|
||||||
|
|
||||||
This is a *complete* transcript of a full gitolite install, *from scratch*,
|
This is a *complete* transcript of a full gitolite install, *from scratch*,
|
||||||
using brand new userids ("sita" on the client, "git" on the server). Please
|
using brand new userids ("sita" on the client, "git" on the server). Please
|
||||||
note that you can use existing userids also, it is not necessary to use
|
note that you can use existing userids also, it is not necessary to use
|
||||||
dedicated user IDs for this. Also, you don't have to use some *other* server
|
dedicated user IDs for this. In particular, people who have a single user
|
||||||
for all this, both server and client can be "localhost" if you like.
|
hosting account can also use this method, as long as they have password access
|
||||||
|
as a fallback if they screw up the keys somewhere. Also, you don't have to
|
||||||
|
use some *other* server for all this, both server and client can be
|
||||||
|
"localhost" if you like.
|
||||||
|
|
||||||
Please note that this entire transcript can be summarised as:
|
Please note that this entire transcript can be summarised as:
|
||||||
|
|
||||||
|
@ -18,14 +38,6 @@ transcript is **non**-gitolite stuff :)
|
||||||
**Please also note that this method will setup everything on the server, but
|
**Please also note that this method will setup everything on the server, but
|
||||||
you have to run it on your workstation, NOT on the server!**
|
you have to run it on your workstation, NOT on the server!**
|
||||||
|
|
||||||
In this document:
|
|
||||||
|
|
||||||
* <a href="#create_userids_on_server_and_client_optional_">create userids on server and client (optional)</a>
|
|
||||||
* <a href="#get_pubkey_access_from_client_to_server">get pubkey access from client to server</a>
|
|
||||||
* <a href="#get_gitolite_source">get gitolite source</a>
|
|
||||||
* <a href="#install_gitolite">install gitolite</a>
|
|
||||||
* <a href="#examine_what_you_have">examine what you have</a>
|
|
||||||
|
|
||||||
----
|
----
|
||||||
|
|
||||||
<a name="create_userids_on_server_and_client_optional_"></a>
|
<a name="create_userids_on_server_and_client_optional_"></a>
|
||||||
|
@ -209,10 +221,27 @@ install mode that allows you to change the defaults etc.
|
||||||
|
|
||||||
----
|
----
|
||||||
|
|
||||||
|
<a name="VERY_IMPORTANT_"></a>
|
||||||
|
|
||||||
|
### VERY IMPORTANT...
|
||||||
|
|
||||||
|
Please read the text that the easy-install command produces as output when you
|
||||||
|
run it. People who fail to read this get into trouble later. And I didn't
|
||||||
|
write all that because I wanted to practice typing.
|
||||||
|
|
||||||
|
The text just above this section is an approximation; your version will
|
||||||
|
contain the correct URLs for your install, including port numbers if
|
||||||
|
non-standard ports were used).
|
||||||
|
|
||||||
|
Try out that `tail -31 ./gl-easy-install` too :)
|
||||||
|
|
||||||
<a name="examine_what_you_have"></a>
|
<a name="examine_what_you_have"></a>
|
||||||
|
|
||||||
### examine what you have
|
### examine what you have
|
||||||
|
|
||||||
|
The last step of the previous command creates a local clone of your
|
||||||
|
gitolite-admin repo in `~/gitolite-admin`.
|
||||||
|
|
||||||
sita@sita-lt:src $ cd ~/gitolite-admin/
|
sita@sita-lt:src $ cd ~/gitolite-admin/
|
||||||
|
|
||||||
sita@sita-lt:gitolite-admin $ git --no-pager log --stat
|
sita@sita-lt:gitolite-admin $ git --no-pager log --stat
|
||||||
|
@ -227,5 +256,15 @@ install mode that allows you to change the defaults etc.
|
||||||
2 files changed, 13 insertions(+), 0 deletions(-)
|
2 files changed, 13 insertions(+), 0 deletions(-)
|
||||||
|
|
||||||
And that's really all. Add keys to keydir here, edit conf/gitolite.conf as
|
And that's really all. Add keys to keydir here, edit conf/gitolite.conf as
|
||||||
needed, then add, commit, and push the changes to the server. Try out that
|
needed, then add, commit, and push the changes to the server.
|
||||||
`tail -31 ./gl-easy-install` too :)
|
|
||||||
|
<a name="emergency_password_access"></a>
|
||||||
|
|
||||||
|
### emergency password access
|
||||||
|
|
||||||
|
If you lose your keys or the worst happens and you use the wrong key for the
|
||||||
|
wrong thing and apparently lose all access, but you still know the password,
|
||||||
|
this is what you do:
|
||||||
|
|
||||||
|
sita@sita-lt:~ $ ssh -o preferredauthentications=password git@server
|
||||||
|
git@server's password:
|
||||||
|
|
Loading…
Reference in a new issue