From: Jakub Narebski <jnareb@gmail.com>
To: "Ciprian Dorin Craciun" <ciprian.craciun@gmail.com>
Cc: sagi4 <geetha@angleritech.com>, git@vger.kernel.org
Subject: Re: configuring git public repository
Date: Fri, 12 Sep 2008 05:57:52 -0700 (PDT) [thread overview]
Message-ID: <m3vdx1o72x.fsf@localhost.localdomain> (raw)
In-Reply-To: <8e04b5820809120533o1e7da548l6868660767a5435d@mail.gmail.com>
"Ciprian Dorin Craciun" <ciprian.craciun@gmail.com> writes:
> On Fri, Sep 12, 2008 at 7:47 AM, sagi4 <geetha@angleritech.com> wrote:
> >
> > Hi all,
> >
> > I am new git..
> >
> > I would like to configure git as a public repository for my rails
> > application..
> >
> > Please help me..
First, I think you can find required information in many documentation
avaliable online, like "Git User's Manual" (distributed with Git), or
Got Community Book from http://git-scm.com
> If I'm correct, you have two major options:
> -- install your own git infrastructure:
> -- by using git-daemon and serving the git repository throught
> git://...;
Note that git:// protocol is meant only for _fetching_ (although you
can configure it for pushing, it is a good option only in very narrow
set of circumstances). And you would have ensure that your firewall
allows git traffic.
> -- by using gitweb? and serving it as http://...;
Gitweb (and cgit, and git-php) is _web interface_ to repository, which
means that you can check the state of repository, view current version
and the log of changes, and many other things from a web browser. All
of those require installing either as CGI module, or some other module
for web server having installed.
To have read-only HTTP access you only need to put your repository in
a place where your web server will see it. Well, that and ensure that
git-update-server-info is run, for clients to be able to know latest
state of the repository. Usually it is done using 'update' hook; it
should be enough to enable example hook (if you use bare repository as
published repository).
To be able to push via HTTP you have to set WebDAV and appropriate
permissions on web server. See the documentation.
> -- by using ssh and serving it as ssh://... (this is
> appropriate mostly for private repositories);
Usually you would want to restrict access by using git-shell, and
perhaps ease configuring permissions using either Gitosis (see also
BlogPosts on git wiki) or ssh_acl.
> -- using an existing Git hosting service like:
> -- (of course) http://repo.or.cz/
> -- http://github.org/
> -- http://gitorious.org/
> -- see also http://git.or.cz/gitwiki/GitHosting
>
> For open-source / public repositories I would opt for using an
> existing hosting service.
For Rails application I would check what other Ruby on Rails people
use. I would guess that it would be either Rubyforge or GitHub.
HTH.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-09-12 12:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 4:47 configuring git public repository sagi4
2008-09-12 12:33 ` Ciprian Dorin Craciun
2008-09-12 12:57 ` Jakub Narebski [this message]
2008-09-12 14:36 ` Lars Hjemli
2008-09-12 14:58 ` CGit and repository list Petr Baudis
2008-09-12 15:10 ` Lars Hjemli
[not found] ` <200809121812.40920.johan@herland.net>
2008-09-12 22:48 ` Petr Baudis
2008-09-12 23:20 ` Lars Hjemli
2008-09-13 19:49 ` Petr Baudis
2008-09-13 20:02 ` Lars Hjemli
2008-09-14 7:53 ` [CGIT PATCH] parsing.c: handle unexpected commit/tag content Lars Hjemli
2008-09-14 8:52 ` Lars Hjemli
2008-09-15 22:04 ` CGit and repository list Lars Hjemli
2008-09-14 17:14 ` Kristian Høgsberg
2008-09-14 17:22 ` Kristian Høgsberg
2008-09-14 18:01 ` Lars Hjemli
2008-09-12 15:54 ` Jakub Narebski
2008-09-12 16:00 ` Shawn O. Pearce
2008-09-12 16:12 ` Lars Hjemli
2008-09-12 16:05 ` Petr Baudis
2008-09-12 16:08 ` Shawn O. Pearce
2008-09-12 16:20 ` Petr Baudis
2008-09-12 16:22 ` Shawn O. Pearce
2008-09-12 17:40 ` Jakub Narebski
2008-09-12 17:45 ` Shawn O. Pearce
2008-09-12 19:13 ` Petr Baudis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3vdx1o72x.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=ciprian.craciun@gmail.com \
--cc=geetha@angleritech.com \
--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.
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 NNTP newsgroup(s).