Gitsune (vosjedev.net)
login
To clone locally:
$ git clone https://betagit.vosjedev.net/git/cgit.git
Last commit: 0658de086a97 ui-shared: link bugs.vosjedev.net for bugs & patches[checkout]
NameSizeMode
.gitignore154B100644
.gitmodules8B100644
.mailmap578B100644
AUTHORS34B100644
COPYING17.67KiB100644
Makefile4.79KiB100644
README3.17KiB100644
cache.c10.8KiB100644
cache.h982B100644
cgit.c35.02KiB100644
cgit.css15.58KiB100644
cgit.h9.19KiB100644
cgit.js1.97KiB100644
cgit.mk4.33KiB100644
cgit.png1.33KiB100644
cgitrc.5.txt34.22KiB100644
cmd.c4.15KiB100644
cmd.h244B100644
configfile.c1.57KiB100644
configfile.h239B100644
contrib/-040000
favicon.ico1.05KiB100644
filter.c11.04KiB100644
filters/-040000
gen-version.sh434B100755
git/ (submodule)-160000
html.c7.22KiB100644
html.h1.3KiB100644
parsing.c4.69KiB100644
robots.txt68B100644
scan-tree.c6.41KiB100644
scan-tree.h15B100644
shared.c13.17KiB100644
tests/-040000
ui-atom.c3.71KiB100644
ui-atom.h118B100644
ui-blame.c7.89KiB100644
ui-blame.h1B100644
ui-blob.c4.51KiB100644
ui-blob.h308B100644
ui-clone.c3.05KiB100644
ui-clone.h151B100644
ui-commit.c4.39KiB100644
ui-commit.h129B100644
ui-diff.c13.02KiB100644
ui-diff.h432B100644
ui-log.c14.84KiB100644
ui-log.h284B100644
ui-patch.c2.76KiB100644
ui-patch.h164B100644
ui-plain.c5.17KiB100644
ui-plain.h1B100644
ui-refs.c5.51KiB100644
ui-refs.h186B100644
ui-repolist.c8.36KiB100644
ui-repolist.h154B100644
ui-shared.c31.89KiB100644
ui-shared.h4.15KiB100644
ui-snapshot.c8.64KiB100644
ui-snapshot.h177B100644
ui-ssdiff.c9.3KiB100644
ui-ssdiff.h495B100644
ui-stats.c9.96KiB100644
ui-stats.h624B100644
ui-summary.c4.22KiB100644
ui-summary.h162B100644
ui-tag.c2.96KiB100644
ui-tag.h101B100644
ui-tree.c1KiB100644
ui-tree.h119B100644
README

Fork notes
==========

This is a softfork of cgit, the one deployed on git.vosjedev.net.
Changes:
- add readme to summary pages
- base on ch/for-jason branch so we get a newer git version (bc why not)


Following is the original README.

cgit - CGI for Git
==================

This is an attempt to create a fast web interface for the Git SCM, using a
built-in cache to decrease server I/O pressure.

Installation
------------

Building cgit involves building a proper version of Git. How to do this
depends on how you obtained the cgit sources:

a) If you're working in a cloned cgit repository, you first need to
initialize and update the Git submodule:

    $ git submodule init     # register the Git submodule in .git/config
    $ $EDITOR .git/config    # if you want to specify a different url for git
    $ git submodule update   # clone/fetch and checkout correct git version

b) If you're building from a cgit tarball, you can download a proper git
version like this:

    $ make get-git

When either a) or b) has been performed, you can build and install cgit like
this:

    $ make
    $ sudo make install

This will install `cgit.cgi` and `cgit.css` into `/var/www/htdocs/cgit`. You
can configure this location (and a few other things) by providing a `cgit.conf`
file (see the Makefile for details).

If you'd like to compile without Lua support, you may use:

    $ make NO_LUA=1

And if you'd like to specify a Lua implementation, you may use:

    $ make LUA_PKGCONFIG=lua5.1

If this is not specified, the Lua implementation will be auto-detected,
preferring LuaJIT if many are present. Acceptable values are generally "lua",
"luajit", "lua5.1", and "lua5.2".


Dependencies
------------

* libzip
* libcrypto (OpenSSL)
* libssl (OpenSSL)
* optional: luajit or lua, most reliably used when pkg-config is available

Apache configuration
--------------------

A new `Directory` section must probably be added for cgit, possibly something
like this:

    <Directory "/var/www/htdocs/cgit/">
        AllowOverride None
        Options +ExecCGI
        Order allow,deny
        Allow from all
    </Directory>


Runtime configuration
---------------------

The file `/etc/cgitrc` is read by cgit before handling a request. In addition
to runtime parameters, this file may also contain a list of repositories
displayed by cgit (see `cgitrc.5.txt` for further details).

The cache
---------

When cgit is invoked it looks for a cache file matching the request and
returns it to the client. If no such cache file exists (or if it has expired),
the content for the request is written into the proper cache file before the
file is returned.

If the cache file has expired but cgit is unable to obtain a lock for it, the
stale cache file is returned to the client. This is done to favour page
throughput over page freshness.

The generated content contains the complete response to the client, including
the HTTP headers `Modified` and `Expires`.

Online presence
---------------

* The cgit homepage is hosted by cgit at <https://git.zx2c4.com/cgit/about/>

* Patches, bug reports, discussions and support should go to the cgit
  mailing list: <cgit@lists.zx2c4.com>. To sign up, visit
  <https://lists.zx2c4.com/mailman/listinfo/cgit>