git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Alan Chandler <alan@chandlerfamily.org.uk>
To: git@vger.kernel.org
Subject: "Publishing your work" questions?
Date: Sat, 20 Aug 2005 14:57:00 +0100	[thread overview]
Message-ID: <200508201457.00725.alan@chandlerfamily.org.uk> (raw)

I am planning my way through switching over to using git (as opposed to 
subversion - via svnserve) to publish some stuff.

At the moment I leave a hole in my firewall for port 3690 and svnserve is run 
as a daemon from inetd.  I use svnserve's own user/realm management to limit 
the repositories I make public.

If I switch over to git, I assume I run git-daemon from inetd.

BUT

a) Is this what the git://my.domain.com/path/to/repository url refers to 
(neither get-pull-script nor git-fetch-script man pages actually say what 
this form means) ?

b) I can't find any mention in the documentation of what the default port 
should be. What is it?

c) Is git-daemon multithreaded (ie do I use nowait in inetd.conf)?

d) Is it possible to ensure that external accesses can't access anywhere in my 
filesystem? 

e) If I put my public key in ~git/.ssh/authorized_keys on the server, I can 
act as user git on the server via ssh.  Does git push support this?  

f) If I can do e), then perhaps [need to read the docs a bit harder] I can set 
up my user git on the machine to use git-receive-pack as its login shell.  
Will this work? - the tutorial talks about needing .bashrc to set up the 
$PATH environment, but are there any other hidden gotchas?

-- 
Alan Chandler
http://www.chandlerfamily.org.uk

             reply	other threads:[~2005-08-20 13:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-20 13:57 Alan Chandler [this message]
2005-08-20 15:52 ` "Publishing your work" questions? Linus Torvalds
2005-08-20 16:12   ` Linus Torvalds
2005-08-20 17:42     ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200508201457.00725.alan@chandlerfamily.org.uk \
    --to=alan@chandlerfamily.org.uk \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).