Hacker News new | past | comments | ask | show | jobs | submit login


If you have ssh access to a box; you have a git remote.

It’s obscenely simple, and contra to your claim the “managed” aspect is not the selling point of this software. The selling point is the project management features and integrations.

In githubs case it’s a managed service.

In gitlabs case, I can be a managed service or it can be a software suite you maintain yourself.

Not a universal truth.

Sure, so now instead of just having a source control remote, you’re now looking after a publicly accessible box in the cloud with all the security headaches that brings. Plus you’ve got to manage credentials essentially manually, make sure people have the right access permissions to repos, look after backups, etc.

I worked at a company that started out with a setup like this for the dev team. It felt like a massive burden was lifted when we moved to Github Enterprise. We weren’t using the project management features at all, just the source code hosting stuff.

Great send me a link to your code. I want to browse it real quick and look over it, before I pull it.

Oh wait, git over ssh doesn't show a web view.

This is actually an absolutely awful idea. Every time I used the code browsing and search features I was disappointed by how poorly the search is working. Lots of false positives. Usually fail to find what I'm looking for. When I git clone something and use my text editor's search feature I usually find what I'm looking for on my first try.

It's not perfect, but for a lot of smaller projects it's fine.

Also way easier to send someone a web link to something in a discussion to have them look into it, especially if it's in a different branch then they may have.

> I want to browse it real quick and look over it, before I pull it

What's wrong with fetching it, checking it out in a local branch, and browsing it using your editor? It probably is much easier to browse the code, see it in context and see the diff using your editor compared to the web interface.

The ssh host doesn't do git hosting. You have a hard time to manage ACLs and have to restrict users accordingly. Also you need to run an http server and update the git cache if you want to support anonymous requests to the repo.

There's a bit more to it ... and sure all can be done manually.

Git hosting over SSH does work. I've seen it work well. We already had ACLs set up for other reasons, and we didn't need anonymous requests. It's the simplest thing that can possibly work; don't add extra complication if it's not needed.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact