git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ciprian Dorin Craciun" <ciprian.craciun@gmail.com>
To: sagi4 <geetha@angleritech.com>
Cc: git@vger.kernel.org
Subject: Re: configuring git public repository
Date: Fri, 12 Sep 2008 15:33:27 +0300	[thread overview]
Message-ID: <8e04b5820809120533o1e7da548l6868660767a5435d@mail.gmail.com> (raw)
In-Reply-To: <19449377.post@talk.nabble.com>

    Hello!

    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://...;
        -- by using gitweb? and serving it as http://...;
        -- by using ssh and serving it as ssh://... (this is
appropriate mostly for private repositories);
    -- 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.

    Hope it's useful for you,
    Ciprian Dorin Craciun.


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..
>
> Thanks
> Sg..
> --
> View this message in context: http://www.nabble.com/configuring-git-public-repository-tp19449377p19449377.html
> Sent from the git mailing list archive at Nabble.com.

  reply	other threads:[~2008-09-12 12:34 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 [this message]
2008-09-12 12:57   ` Jakub Narebski
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=8e04b5820809120533o1e7da548l6868660767a5435d@mail.gmail.com \
    --to=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).