Live data from Hacker News

Set up your private Git hosting with Gogs

obahua.com

21–30 of 39 posts

Re: Set up your private Git hosting with Gogs

#21
post #4

Looks much easier to deploy than Gitlab.

I was actually just thinking about how this clone would make a good blog post pointing out the pain that hovers around many substantial ruby/rails projects versus other tool sets. To be able to download the binary and just run a web app ... amazing. Considering the last time I tried to run Gitlab all kinds of libraries didn't install properly and workers wouldn't come up when they were supposed to.

Re: Set up your private Git hosting with Gogs

#22
Besides the ease of installation, the thing that most impresses me is the very low resource usage and amazing responsiveness on even a tiny VPS.

    PID USER      PRI  NI  VIRT   RES   SHR S CPU% MEM% TIME+  Command
  31378 smw        20   0  262M 11516  5712 S  0.0  0.6 0:00.00 ./gogs web
11 MB of RSS? Quoting user 'pas' in an earlier comment, Gitlab wants about 2GB.

I have no idea how well it scales to a large user base, but I feel like this is going to become the go to option for side projects where you just want to share some private code with a friend or two.

Re: Set up your private Git hosting with Gogs

#24
post #19
post #3

Gitlab is an option as well. I found the README in their Github repo has additional info: https://github.com/gogits/gogs It seems like they intend to manipulate git entirely from Go. Interesting stuff!

Serious question about Gitlab and something that has always scared me away: How does it perform on a resource-constrained system? A lot of the hardware requirements[1] are presented in terms of users, but the "minimum" RAM requirement seems really high. If I wanted to use this with a small team (~20 users) in a resource constrained environment it seems like it'd be way overkill. [1]: https://gitlab.com/gitlab-org/git…

The ram usage is very high for an application of this type, if you compare it to something like Indefero [1]. The minimum requirements on the page you linked seem correct.

[1]: http://projects.ceondo.com/p/indefero/

Re: Set up your private Git hosting with Gogs

#26
post #10

Noticed the release notes mention a forced password reset for all users because of a hash change. Couldn't that be avoided by storing the hash type/version, and silently upgrade on the next successful login (when the password is available briefly in plaintext in the login request)?

This is what Django does. Works very well.

Re: Set up your private Git hosting with Gogs

#28

Complicate deployment is one of the major reason for me to stay away from using Self-hosted Git Server for my small team. This one looks really interesting and promising. Being open source project is another major bonus.

On Debian-based systems you can install the gitolite package (from the repo) and then run: sudo dpkg-reconfigure gitolite. You can then start pushing and pulling.

Re: Set up your private Git hosting with Gogs

#29
post #11

I like it, but the blatant copy of the Github design makes me wonder: could one run a public Gogs instance ? Anyway, that's a really slick work. Once again Go shines and make that project super easy to install.

To be honest, I would say that Gitlab is more of a copy of Github than this project, and so far I haven't seen any problem with Gitlab.

Re: Set up your private Git hosting with Gogs

#30
post #19
post #3

Gitlab is an option as well. I found the README in their Github repo has additional info: https://github.com/gogits/gogs It seems like they intend to manipulate git entirely from Go. Interesting stuff!

Serious question about Gitlab and something that has always scared me away: How does it perform on a resource-constrained system? A lot of the hardware requirements[1] are presented in terms of users, but the "minimum" RAM requirement seems really high. If I wanted to use this with a small team (~20 users) in a resource constrained environment it seems like it'd be way overkill. [1]: https://gitlab.com/gitlab-org/git…

Good point, I've just changed the RAM requirement since it was a bit outdated, see https://gitlab.com/gitlab-org/gitlab-ce/commit/01799721dc6cb... for the change and new version on https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst...
Post reply on HN