3 ms·

Ok, git_noobie here. What is git http-backend [1] for then? [1] https://git-scm.com/docs/git-http-backend https://git-scm.com/docs/git-http-backend I discover

• eichin 3y ago
  If you want to use git through a web server, it's one way of doing that. (For example, if you want to use some existing http auth for your users.) You don't particularly need to do that - it's just an option; git over ssh works fine too, as does git with file: local urls (or without "remotes" at all.) Professionally, ssh auth (especially with ControlPersist) has always been the better/faster option, but that's more of a cultural thing. (My hobby workflow is to just start writing in a directory, and then after a little bit do a "git init"... and then once I have enough to pick a name, I have a "git save-project projectname" script that goes off and does a git init --bare on a homelab server and git push --set-upstream so it's now a remote. Just gradually escalating how "seriously" I'm treating it and therefore how much plumbing I bother with.)
• Jenk 3y ago
  git help -a lists all available commands. It's important to note that the git binaries are (usually) both client and server - by design what with the hole "decentralised" thing. So the default package will let you run server functionality such as the http-backend (which allows the machine you run it on to serve http(s):// schema repositories)