Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to Host Your Own Private Git Repositories

eklitzke.org

Post reply on HN
Print view View original

71–80 of 114 posts

Re: How to Host Your Own Private Git Repositories

#71

Post by Mo3 »

kewleus wrote: post #65
treve wrote: post #60

Earlier quoted context omitted.

Gitlab is massive though. I think it's a great solution for teams on dedicated hardware, but if you need something quick, low-maintenance and lightweight Gitlab might be a bit overkill.

You can't get much quicker or low maintenance than gitlab, though it is definitely not lightweight.

Gogs? Gitolite?

Re: How to Host Your Own Private Git Repositories

#72

Post by taneq »

Jach wrote: post #38
dbg31415 wrote: post #30

Earlier quoted context omitted.

But... you are using another online service to host the service yourself, no? And presumably they are also throwing in backups and redundancy of some sort... certainly it would take you a minute to set those things up, test them, monitor they are working... And isn't GitHub basically like everyone's resume these days? I don't know... at some point you sort of just have to trust someone... be it the hosting provider,…

It's especially sad because git is distributed and every time there's a GitHub outage I hear online some teams are blocked for the day. But everyone has the whole repo. You're not screwed like if your SVN or Perforce server goes down. Anyone could become the new "remote to push to / pull from" until the outage is resolved, or you could set up one of these bare repos somewhere pretty quick. When the outage is resolved…

This is what happens when people cargo-cult git because it's what the cool kids are doing, instead of actually making an informed choice.

Re: How to Host Your Own Private Git Repositories

#74

Post by sigil »

stephenr wrote: post #70
sigil wrote: post #49

Earlier quoted context omitted.

This is precisely what I do. But, I'd prefer it if git-shell didn't let users probe and read git repositories at any absolute path on the remote end. That's not great behavior for a restricted shell.

Remove the 'others' read/execute permission from user home directories.

Sure, but there might be git repos sitting around elsewhere. Why risk exposing a git repo literally anywhere in the filesystem to a restricted shell account?

Re: How to Host Your Own Private Git Repositories

#75

Post by stephenr »

sigil wrote: post #74
stephenr wrote: post #70

Earlier quoted context omitted.

Remove the 'others' read/execute permission from user home directories.

Sure, but there might be git repos sitting around elsewhere. Why risk exposing a git repo literally anywhere in the filesystem to a restricted shell account?

Then use a chroot.

Re: How to Host Your Own Private Git Repositories

#77

Post by sigil »

stephenr wrote: post #75
sigil wrote: post #74

Earlier quoted context omitted.

Sure, but there might be git repos sitting around elsewhere. Why risk exposing a git repo literally anywhere in the filesystem to a restricted shell account?

Then use a chroot.

You could do that, but that means for a shared repo and N git shell accounts you've got N chroots, presumably using null or bind mounts.

That's a lot more work than a restricted shell which just...restricts.

Re: How to Host Your Own Private Git Repositories

#78

Post by philsnow »

If you don't need code review and don't mind a hosted solution, you can get by with the AWS free tier and use IAM for all your access control.

    AWS CodeCommit:
    5 active users per month
    50 GB-month of storage per month
    10,000 Git requests per month
    Does not expire at the end of your 12 month AWS Free Tier term.
https://aws.amazon.com/s/dm/optimization/server-side-test/fr...
Post reply on HN