4 ms·
A git server is just a computer with ssh access, though. Git itself is designed in a way where it doesn't even need a server. If you keep it simple, it stays s
by marginalia_nu 5y ago
A git server is just a computer with ssh access, though. Git itself is designed in a way where it doesn't even need a server.
If you keep it simple, it stays simple.
- nijave 5y agoSure but the article isn't talking about a "git" server. It's talking about replacing Github with Gitlab which is a fully integrated developer workflow tool with code review functionality. They use "Git server" a lot in the article, but the opening and closing both specifically mention a Github replacement.
- marginalia_nu 5y agoRight, but git itself has no concept of code reviews, if that's what you want, maybe you shouldn't be looking for a git server, but some mechanism for code reviews.
- jeltz 5y agoYes? That is presumably exactly what they are looking for. They just worded it poorly. The reason people use GitHub and Gitlab is usually not because they want a git server. For that there are much better tools like gitolite.
- maccard 5y agoA postgres server is just a computer with 5432 open instead of 22. > If you keep it simple, it stays simple. Things that work well for one person in isolation don't work at scale or for teams. How do you handle authentication for your git server? What about backups? Manage disk space? Updates? That's before you get to the point of dealing with workflows and integrations, or "it's slow when 10 people clone at the same time"
- marginalia_nu 5y agoEvery cloned git repository is a backup. That's like the entire point of git. It's decentralized version control. This is why the notion of a "git server" is a bit of an oxymoron. Most of the things you're struggling to solve are effectively preventing it from actually working as intended.
- RealStickman_ 5y agoYou don't want to ask your users for their local backup Edit: To expand on my comment a bit. 1. You will have to check with every user when they last pulled their repos and/or made any local change and wanted to push it. 2. While your git is offline and you're figuring out which version is the most up to date your users can't do any work with git 3. You just lost all your issues, pull requests, wiki articles and more that isn't stored in git 4. Making backups is your job as a systems administrator and you just failed spectacularly
- maccard 5y ago> Every cloned git repository is a backup Is it? If I checksum the .git folder on my workstation and my co-workers workstation they're going to come back different. There's no guarantees that I haven't rebased main, or that I have all of the branches that were stored on the remote. If something catastrophic happens to our main remote, which one of our versions do we restore to? > It's decentralized version control. Just because git is decentralised, doesn't mean that it can only be used in a decentralised way. How many teams are pushing/pulling like a p2p network, and deploying to servers/clients from their workstations and verifying that the commit hash of their local repository matches what's deployed? A vanishingly small number of people. > Most of the things you're struggling to solve are effectively preventing it from actually working as intended If everyone is using it wrong, the tool is wrong. There are billion dollar companies out there that are based on a centralised git service, which proves that people can (and do) use tools in the way that makes sense, not necessarily as they were designed. Personally I'm glad I don't have to share patches over mailing lists with my coworkers, but you do you.
- 5y ago
- jjtheblunt 5y agoSo what's running on machine X so that it can function as a remote for git pull etc?
- TacticalCoder 5y ago> So what's running on machine X so that it can function as a remote for git pull etc? SSH and Git.
- jjtheblunt 5y agosshd can't alone be it...i bet there must be an account for git to access on the server when reaching out from the "client" / peer.