| Age | Commit message (Collapse) | Author | Lines |
|
|
|
|
|
|
|
|
|
cgit's built-in clone support speaks the dumb HTTP protocol, which
serves static files that only `git update-server-info` refreshes.
Without this hook a clone can miss refs pushed after the repository
was created.
|
|
The wiring has real pitfalls around PATH_INFO and the link base, so
these ship as working commented configs. nginx needs the fcgiwrap
bridge while apache and lighttpd run the CGI directly. The security
headers live here rather than in cgit because they must also cover
the static assets the server serves itself.
|
|
|
|
The C sources move to source/, the served files to assets/, the bundled
Git submodule to libraries/git and the filter scripts to extensions/.
Everything the build generates now lands in build/, so a clean is a
single remove and the tree stays clean.
|