mono.git/hostnix/elmo/git.nix, branch testUnnamed repository; edit this file 'description' to name the repository.http://git.mou.fo/2026/mono.git/atom/hostnix/elmo/git.nix?h=test2026-04-15T22:50:14Zelmo: make upgrade, cgit fixup2026-04-15T22:50:14ZJoe Moudev@mou.fo2026-04-14T03:50:58Zurn:sha1:ad46641b2913b46c6b01694d86470dd3b464e154
git-daemon-export-ok is a very simply access control for
git-http-backend. We explicitly disable it.
See https://github.com/NixOS/nixpkgs/commit/8b6fc43e100d053ed4e7fd28f4f1edf04f0d5374
Add mojo to git2026-04-14T03:47:43ZJoe Moudev@mou.fo2026-03-17T22:59:50Zurn:sha1:f975c0931acd1420f7ac006dafc965e6fb57036bcgit clone URL2026-02-04T18:58:53ZJoe Moudev@mou.fo2026-01-24T15:43:29Zurn:sha1:628501e567068bba3f0ccbe6cbc39cb35d0b3dc7Add doughboy2025-12-29T07:19:20ZJoe Moudev@mou.fo2025-12-21T02:45:43Zurn:sha1:af8f19135c5dd62cc336687431986af96f681eb3Stripped down git hosting with cgit and git-shell2025-06-27T22:07:20ZJoe Moudev@mou.fo2024-12-23T21:36:27Zurn:sha1:a13fb60da18e16c20c7a160eac6a9f700058e55a
Advantages over Gitea (and most other git forges):
- Arbitrary repository hierarchies.
- Repository aliases with symlinks.
- No metadata to keep synchronized with repositories; simple automation.
Create new repos like:
$ sudo -u git git init --bare -b main /srv/git/2025/calmux.git
Ideally we would not require authentication for whitelisted public
repos. This is difficult with oauth2-proxy because to disable
auth_request we need a new location clause which does not "inherit" the
FastCGI configuration. Perhaps we could use cgit's built-in auth-filter.
Considered gitolite instead of git-shell (which would allow multiuser
authentication). This probably requires configuring each repo which
complicates automation.
Try out Gitea2024-10-09T17:48:41ZJoe Moudev@mou.fo2024-06-26T00:44:22Zurn:sha1:19805b91322878264cc235c880c04fdabafa0949
DISABLE_REGISTRATION needs to be set after the initial administrator
account is manually registered.
Considered the Forgejo community fork, but it doesn't seem to have
attracted very much of the developer community. Despite concerns about
copyright claims, Gitea does not have a CLA; it is MIT licensed. Still
considering even lighter weight options that may be easier to
programmatically control (just an HTTP server that speaks the smart
protocol?).
For managing groups of repositories, can use labels or organizations.
Neither seem particularly convenient.
Gitea defaults to public repositories.