configuring git public repository

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.

Quoted 9 lines · On Fri, Sep 12, 2008 at 7:47 AM, sagi4 <[email protected]> wrote:

Hi all,

I am new git..

I would like to configure git as a public repository for my rails application..

Please help me..

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.

Quoted 6 lines · Ciprian Dorin Craciun

Quoted 5 lines · On Fri, Sep 12, 2008 at 7:47 AM, sagi4 <[email protected]> wrote:

Hi all,

I am new git..

Quoted 4 lines

Quoted 2 lines

I would like to configure git as a public repository for my rails application..

   -- 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.

<plug>
Current cgit also allows cloning over http using the same url as for browsing the repo, i.e. you may

  $ git clone http://hjemli.net/git/cgit

This has one advantage over just publishing the repo; you don't have to run git-update-server-info (thanks to the work done by Shawn O. Pearce on git-http-backend, which is shamelessly reimplemented in cgit).
</plug>

Quoted 7 lines · Lars Hjemli

<plug>
Current cgit also allows cloning over http using the same url as for browsing the repo, i.e. you may

  $ git clone http://hjemli.net/git/cgit

Quoted 5 lines

This has one advantage over just publishing the repo; you don't have to run git-update-server-info (thanks to the work done by Shawn O. Pearce on git-http-backend, which is shamelessly reimplemented in cgit).
</plug>

this finally tripped me over and I wanted to quickly add cgit as an
alternate viewing interface at repo.or.cz. [...]

Quoted 3 lines · Petr Baudis

this finally tripped me over and I wanted to quickly add cgit as an
alternate viewing interface at repo.or.cz. [...]

Or you can wait a little while for "smart" HTTP server, which I guess also generates automatically or/and on the fly objects/info/packs and info/refs required by "dumb" protocols clients (including old HTTP clients).

P.S. Could you please gather some statistics to compare the period before and after installing "smart" HTTP server (and after smart clients became widespread).

Quoted 9 lines · Jakub Narebski

Quoted 3 lines · Petr Baudis

this finally tripped me over and I wanted to quickly add cgit as an
alternate viewing interface at repo.or.cz. [...]

Or you can wait a little while for "smart" HTTP server, which I guess also generates automatically or/and on the fly objects/info/packs and info/refs required by "dumb" protocols clients (including old HTTP clients).

The automatic generation of objects/info/packs and info/refs is planned for support in the smart CGI, but it doesn't help the "gitweb URL is same as clone URL" concept. For that you need your HTTP server to know how to issue some requests to gitweb and others to the smart CGI or to the filesystem.

Quoted 4 lines

P.S. Could you please gather some statistics to compare the period before and after installing "smart" HTTP server (and after smart clients became widespread).

Well, it would help if there was a working implementation of the "smart" HTTP server. ;-)

Quoted 14 lines · Petr Baudis

Quoted 12 lines · Lars Hjemli

<plug>
Current cgit also allows cloning over http using the same url as for browsing the repo, i.e. you may

  $ git clone http://hjemli.net/git/cgit

This has one advantage over just publishing the repo; you don't have to run git-update-server-info (thanks to the work done by Shawn O. Pearce on git-http-backend, which is shamelessly reimplemented in cgit).
</plug>

Quoted 2 lines

this finally tripped me over and I wanted to quickly add cgit as an
alternate viewing interface at repo.or.cz. [...]

Or you can wait a little while for "smart" HTTP server, which I guess also generates automatically or/and on the fly objects/info/packs and info/refs required by "dumb" protocols clients (including old HTTP clients).

P.S. Could you please gather some statistics to compare the period before and after installing "smart" HTTP server (and after smart clients became widespread).

Quoted 3 lines · Jakub Narebski

P.S. Could you please gather some statistics to compare the period before and after installing "smart" HTTP server (and after smart clients became widespread).

What kind of statistics?

Quoted 6 lines · Petr Baudis

Quoted 3 lines · Jakub Narebski

P.S. Could you please gather some statistics to compare the period before and after installing "smart" HTTP server (and after smart clients became widespread).

Quoted 1 line

What kind of statistics?

Disk IO and network IO consumed probably. The kernel.org folks are hoping the smart HTTP server can lower their loads a bit by being more careful about what we send to the client.

Quoted 4 lines

Disk IO and network IO consumed probably. The kernel.org folks are hoping the smart HTTP server can lower their loads a bit by being more careful about what we send to the client.

To check whether it actually matters for me, I have counted HTTP requests for info/refs: 42 per hour for the last 5.5 days. So it might. 28% of the requests are web crawlers.

For objects/../, it is more fun - 1942 requests per hour. 46% is accounted for web crawlers. I will put up a robots.txt. ;-)

Quoted 4 lines · Jakub Narebski

P.S. Could you please gather some statistics to compare the period before and after installing "smart" HTTP server (and after smart clients became widespread).

What kind of statistics?

Quoted 7 lines · Petr Baudis

Quoted 4 lines · Jakub Narebski

P.S. Could you please gather some statistics to compare the period before and after installing "smart" HTTP server (and after smart clients became widespread).

What kind of statistics?

In short: check how "smart" HTTP protocol would improve things.

Quoted 6 lines · Petr Baudis

Quoted 4 lines · Jakub Narebski

P.S. Could you please gather some statistics to compare the period before and after installing "smart" HTTP server (and after smart clients became widespread).

Quoted 1 line

What kind of statistics?

In the simplest case just some averaged system load (perhaps load average from uptime, or from top, or from /proc) before and after. Perhaps bandwidth used per week or something like that too.

If you have time and interest, CPU load, disk IO, network IO or network bandwidth used, and average time to serve request (latency) for fetching via HTTP protocol, for "dumb" and "smart" clients, perhaps averaged over number of requests. (I don't know unfortunately how to get such data).

In short: check how "smart" HTTP protocol would improve things.

it seems that cgit
requires all the repositories explicitly listed in the config file. Do you plan to remove this limitation in the future?

Quoted 10 lines · Lars Hjemli

Quoted 3 lines · Petr Baudis

it seems that cgit
requires all the repositories explicitly listed in the config file. Do you plan to remove this limitation in the future?

Not really, I'd rather add another command (or a commandline option) to generate an include-file for cgitrc by scanning directory-trees for git repos. I've CC'd Kristian since I believe he's got such a script running for freedesktop.org; if so, maybe it could be included/used as basis for something similar in cgit?

Here's a script I wrote for locating repos and generating repo lists/configs for cgit, gitweb and hgwebdir (yes, this handles hg repos as well). It works either as a CGI script (producing a list of detected repos in HTML format), or from the command-line. It's only been tested on an experimental DVCS server at $dayjob, so you might have to change things to make it work in your scenario.

If there is interest in this, I can create a public repo and we can keep improving on it.

Quoted 19 lines · Johan Herland

Quoted 10 lines · Lars Hjemli

Quoted 3 lines · Petr Baudis

it seems that cgit
requires all the repositories explicitly listed in the config file. Do you plan to remove this limitation in the future?

Not really, I'd rather add another command (or a commandline option) to generate an include-file for cgitrc by scanning directory-trees for git repos. I've CC'd Kristian since I believe he's got such a script running for freedesktop.org; if so, maybe it could be included/used as basis for something similar in cgit?

Here's a script I wrote for locating repos and generating repo lists/configs for cgit, gitweb and hgwebdir (yes, this handles hg repos as well). It works either as a CGI script (producing a list of detected repos in HTML format), or from the command-line. It's only been tested on an experimental DVCS server at $dayjob, so you might have to change things to make it work in your scenario.

Quoted 2 lines

If there is interest in this, I can create a public repo and we can keep improving on it.

Thanks. The script was a bit more scary than I thought, but in the end I managed to generate something. There are trailing dots in project names, but I'm not going to waste time on that anymore - this has long gone over the 20 minutes I originally alotted the project anyway; I hope cgit will gain a builtin capability for this in the future, since this is still quite a pain. Attached is a random patch for your script I had to use, FWIW.

The script we're using on freedesktop.org is something like this:

http://people.freedesktop.org/~krh/find-repos.sh

which isn't too scary. We run it from a cron script, every ten minutes or so. It's much better than rescanning all the dirs every time somebody requests the repo listing (we have a lot of repos, check cgit.freedesktop.org). We have no need for cgit to to this automatically on every request, and I don't see us using that feature if it gets implemented.

Quoted 3 lines · Kristian Høgsberg

The script we're using on freedesktop.org is something like this:

http://people.freedesktop.org/~krh/find-repos.sh

Quoted 7 lines

which isn't too scary. We run it from a cron script, every ten minutes or so. It's much better than rescanning all the dirs every time somebody requests the repo listing (we have a lot of repos, check cgit.freedesktop.org). We have no need for cgit to to this automatically on every request, and I don't see us using that feature if it gets implemented.

A feature that would be useful, though, would be support for listing a sub-set of repos... for example, cgit.freedesktop.org/~krh would list just my repos and cgit.freedesktop.org/xorg/driver would list all the X.org driver repos.

Another idea is a javascript/css frontpage that
supports folding repos away according to the groups and possibly common path elements in the url.

Quoted 19 lines · Johan Herland

Quoted 10 lines · Lars Hjemli

Quoted 3 lines · Petr Baudis

it seems that cgit
requires all the repositories explicitly listed in the config file. Do you plan to remove this limitation in the future?

Not really, I'd rather add another command (or a commandline option) to generate an include-file for cgitrc by scanning directory-trees for git repos. I've CC'd Kristian since I believe he's got such a script running for freedesktop.org; if so, maybe it could be included/used as basis for something similar in cgit?

Here's a script I wrote for locating repos and generating repo lists/configs for cgit, gitweb and hgwebdir (yes, this handles hg repos as well). It works either as a CGI script (producing a list of detected repos in HTML format), or from the command-line. It's only been tested on an experimental DVCS server at $dayjob, so you might have to change things to make it work in your scenario.

Quoted 2 lines

If there is interest in this, I can create a public repo and we can keep improving on it.

Thanks. The script was a bit more scary than I thought, but in the end I managed to generate something. There are trailing dots in project names, but I'm not going to waste time on that anymore - this has long gone over the 20 minutes I originally alotted the project anyway; I hope cgit will gain a builtin capability for this in the future, since this is still quite a pain.

Unfortunately, the recommended RewriteRule is not working - it does not play well together with query parameters cgit is using, so e.g. browsing past commits does not work. What RewriteRule should I use instead?

I guess I could add support for something like

scan-paths=/pub/git

in cgitrc (and optionally store the result of the scan as another cgitrc-file in the cache directory). Would that improve things for you?

Quoted 3 lines

Unfortunately, the recommended RewriteRule is not working - it does not play well together with query parameters cgit is using, so e.g. browsing past commits does not work. What RewriteRule should I use instead?

On hjemli.net I used to specify "virtual-root=/git" in cgitrc combined with this rule in /etc/apache/httpd.conf

RewriteRule ^/git/(.*)$ /cgit/cgit.cgi?url=$1 [L,QSA]

Quoted 7 lines · Lars Hjemli

I guess I could add support for something like

scan-paths=/pub/git

in cgitrc (and optionally store the result of the scan as another cgitrc-file in the cache directory). Would that improve things for you?

Yes, certainly.

I wonder why

       http://repo.or.cz/c/libc.git/

has such a funny-looking summary page.

Let me know if you want me to update cgit there sometime. In the next days I will add some means for switching between cgit and gitweb views.

Quoted 7 lines · Lars Hjemli

I guess I could add support for something like

scan-paths=/pub/git

in cgitrc (and optionally store the result of the scan as another cgitrc-file in the cache directory). Would that improve things for you?

Yes, certainly.

Quoted 3 lines

Quoted 3 lines

Unfortunately, the recommended RewriteRule is not working - it does not play well together with query parameters cgit is using, so e.g. browsing past commits does not work.

I wonder why

       http://repo.or.cz/c/libc.git/

has such a funny-looking summary page.