4 ms·

But why? If you have an SSH server running, you can immediately setup a git server. Just do git init —-bare, no gigantic web server overhead. https://rgz.ee/gi

But why? If you have an SSH server running, you can immediately setup a git server. Just do git init —-bare, no gigantic web server overhead. https://rgz.ee/git.html https://rgz.ee/git.html

bee_rider 4y ago
It is easy to give people read-only git access no SSH, if you want to share your code with the internet at large?
- jpe90 4y ago
  If you add a git-daemon-export-ok file to the repo, it's accessible read-only over the git protocol. That's how all my repos on https://git.jeskin.net https://git.jeskin.net are setup. https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protoco...
- bee_rider 4y ago
  note: Transposing "it" and "is" has made my question look sort of passive-aggressive or sarcastic, this was accidental.
  - jpe90 4y ago
    The intent was clear from the context, no worries!
throwaway894345 4y ago
Presumably people value the UI (also, what is the "gigantic web server overhead" you're referring to?).
- megous 4y ago
  Ever tried to install gitlab? It's like 1GiB compressed package. lol
  - layer8 4y ago
    Gitea is much more lightweight.
nine_k 4y ago
Gitlab has a nice GUI, team features, and CI/CD integration. It's a reasonable choice for a team. I also remember the there were tools that use Git as a backend for a change review system, and for an issue-tracking system (much like the stuff which Fossil has integrated). With that, you theoretically don't need a central server at all, as long as you can send patches to each other. In practice, a central server is an important convenience that helps keep the history synchronized between several developers.
slow_typist 4y ago
Yeah you could even use recent ssh clients if you leave gitea, which is written in go, out of the equation: https://github.com/go-gitea/gitea/issues/17798 https://github.com/go-gitea/gitea/issues/17798

But why? If you have an SSH server running, you can immediately setup a git server. Just do git init —-bare, no gigantic web server overhead. https://rgz.ee/git.html https://rgz.ee/git.html

bee_rider 4y ago

It is easy to give people read-only git access no SSH, if you want to share your code with the internet at large?

jpe90 4y ago
If you add a git-daemon-export-ok file to the repo, it's accessible read-only over the git protocol. That's how all my repos on https://git.jeskin.net https://git.jeskin.net are setup. https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protoco...
bee_rider 4y ago
note: Transposing "it" and "is" has made my question look sort of passive-aggressive or sarcastic, this was accidental.
- jpe90 4y ago
  The intent was clear from the context, no worries!

throwaway894345 4y ago

Presumably people value the UI (also, what is the "gigantic web server overhead" you're referring to?).

megous 4y ago
Ever tried to install gitlab? It's like 1GiB compressed package. lol
- layer8 4y ago
  Gitea is much more lightweight.

nine_k 4y ago

Gitlab has a nice GUI, team features, and CI/CD integration. It's a reasonable choice for a team. I also remember the there were tools that use Git as a backend for a change review system, and for an issue-tracking system (much like the stuff which Fossil has integrated). With that, you theoretically don't need a central server at all, as long as you can send patches to each other. In practice, a central server is an important convenience that helps keep the history synchronized between several developers.

slow_typist 4y ago

Yeah you could even use recent ssh clients if you leave gitea, which is written in go, out of the equation: https://github.com/go-gitea/gitea/issues/17798 https://github.com/go-gitea/gitea/issues/17798