Live data from Hacker News

You already have a Git server

maurycyz.com

41–50 of 454 posts

Re: You already have a Git server

#41
post #38

I tried this and it is never as smooth as described. Why is GitHub popular? its not because people are "dumb" as others think. Its because GitHub "Just Works". You don't need obscure tribal knowledge like seba_dos1 suggests [0] or this comment https://news.ycombinator.com/item?id=45711294 The official Git documentation for example has its own documentation that I failed to get work. (it is vastly different from what…

Are basic git concepts like bare repos "obscure tribal knowledge" these days? What do you think ".git" directory is?

Having to make a repo bare to not have issues with branches is definitely obscure.

Re: You already have a Git server

#44
post #41

Earlier quoted context omitted.

Are basic git concepts like bare repos "obscure tribal knowledge" these days? What do you think ".git" directory is?

Having to make a repo bare to not have issues with branches is definitely obscure.

It wasn't obscure before GitHub.

Still, I like the online browser, and pr workflow.

Re: You already have a Git server

#46
post #41

Earlier quoted context omitted.

Are basic git concepts like bare repos "obscure tribal knowledge" these days? What do you think ".git" directory is?

Having to make a repo bare to not have issues with branches is definitely obscure.

It's obvious as soon as you consider that your push will overwrite a ref that's currently checked out in the target's repo workdir. The exact same thing happens when pushing to local repos. You don't have to make a repo bare to avoid this issue, but it's certainly the easiest way to avoid it altogether when you don't need a workdir on the server side.

Re: You already have a Git server

#47
post #3

Interesting. I am just trying to decide between self-hosting Forgejo and other options for hosting Git in own private network.

One of my favorite tools available for Linux is called gitolite. It's in the Debian repo.

https://gitolite.com/gitolite/

If you think the bare bones example is interesting and want something simple just for you or a small group of people, this is one step up. There's no web interface. The admin is a git repository that stores ssh public keys and a config file that defines repo names with an ACL. When you push, it updates the authorization and inits new repositories that you name.

I put everything in repos at home and a have multiple systems (because of VMs) so this cleaned things up for me considerably.

Re: You already have a Git server

#48
post #26

Earlier quoted context omitted.

Could also consider running a Tangled knot (lightweight, headless git servers): https://tangled.org

Does this support private repositories with collaboration?

Not yet, unfortunately. Mostly due to protocol limitations—we use AT (https://atproto.com) for federation.

Re: You already have a Git server

#50
post #38

I tried this and it is never as smooth as described. Why is GitHub popular? its not because people are "dumb" as others think. Its because GitHub "Just Works". You don't need obscure tribal knowledge like seba_dos1 suggests [0] or this comment https://news.ycombinator.com/item?id=45711294 The official Git documentation for example has its own documentation that I failed to get work. (it is vastly different from what…

Are basic git concepts like bare repos "obscure tribal knowledge" these days? What do you think ".git" directory is?

The vast majority of developers working with git daily don’t know what a bare repo is, or that it exists at all. It’s not obscure knowledge as such, it’s just never come up for them as something they need.
Post reply on HN