Gogs, an alternative to Gitlab • Hacker News Board

Re: Gogs, an alternative to Gitlab

#211

Post by yoklov » Tue, Mar 17, 2015, 3:08 AM UTC

67726e wrote: post #176

gkoberger wrote: post #133

I love OSS, however I hate this argument: "You could certainly purchase access to private Github repositories, but most certainly you’d rather want to invest your capital in more pressing matters." That's their #1 reason? GitHub is, like, $7. If that saves you 10 minutes of having to maintain your own servers? Completely seems worth it to me. Or, GitLab or BitBucket have free private repos. My argument is this: your…

Well, your salary is something of a sunk cost. Now depending on the amount of time spent managing that GitLab server, it might make financial sense. If it is truly easy to maintain as they seek, and claim, then it just might make sense. Consider the organization that needs hosted GitHub enterprise - a pricey proposition. Unless you could otherwise have spent your time working on a feature that would directly increase…

GitLab has been ridiculously easy to manage for us. Really my only complaint is that it's slow as all hell, and gives up too early on a lot of pages because of this.

Still, compared to the Perforce server crashing every other week (a slight exaggeration, but still), it's a marked improvement.

Re: Gogs, an alternative to Gitlab

#212

Post by mholt » Tue, Mar 17, 2015, 3:10 AM UTC

Vendan wrote: post #207

Just as a warning, I don't consider gogs to be stable enough for production use. There's data race errors that pop up, resulting in errors resolving various assets. I've had everything from user's avatar icons to the main homepage randomly error out as 404. The dev doesn't seem to understand that data races, i.e. unsafe cross thread data access, is an issue. In addition, note that it and least some of the libraries i…

> note that it and least some of the libraries it uses are written by devs for whom english is at best a second language, so expect difficulties communicating

Considering that English is not their native language, I'd say they're doing pretty darn well so far. Speaking with at least one of the developers personally and via email, I've never had any trouble.

> don't expect assistance from the community

Well that's a mighty presumptuous thing to say about a lot of good people. By and large, the Go community likes Gogs and its developers. I've met Jiahua personally. He's a solid guy and one really dedicated developer. Overall, the Go community wants Gogs to be great.

If you don't like Gogs, you don't have to use it. But you're raising a warning about it because you think the Go community treats it like some sort of poison and that the developers are incompetent. Neither are true.

Re: Gogs, an alternative to Gitlab

#213

Post by sytse » Tue, Mar 17, 2015, 3:45 AM UTC

orthecreedence wrote: post #187

sytse wrote: post #153

Earlier quoted context omitted.

I'm sorry to hear that GitLab didn't seem to work with multiple requests. The way to resolve this is to configure multiple unicorn workers, please see https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc... On GitLab.com we have 20+ unicorn workers that handle over 30k monthly active users.

Cool, thanks for reaching out! I'll look into this. Finding info about this problem was a chore, so I'm really appreciative you're able to point me somewhere =].

You're welcome, I tried to improve the documentation so that it is easier to find https://gitlab.com/gitlab-org/gitlab-ce/commit/9269606c94853...

Re: Gogs, an alternative to Gitlab

#214

Post by nine_k » Tue, Mar 17, 2015, 3:48 AM UTC

awalGarg wrote: post #125

nine_k wrote: post #95

Earlier quoted context omitted.

The implementation language has a lot of implications. * I'm extra wary installing anything written in e.g. PHP: it has a higher chance to be remotely crackable. * I plan for more CPU and expect higher latency if something I need to run is written in e.g. Ruby. * I plan for extra RAM and JVM tweaking for things written in Java (or Scala). * I expect extra setup hassles for things written using Node. Upsides are easy…

> e.g. PHP: it has a higher chance to be remotely crackable No language war/php sucks discussion, but this isn't even remotely true :/

PHP itself might be fine, but it is very widely used, and thus very thoroughly attacked. Unfortunately, a lot of sloppy code still historically exists in PHP. PHP itself is not inherently unsafe, of course.

By the same token, if I deploy a network-facing app that invokes a lot of C code (as opposed to e.g. bytecode), I must be aware of a higher probability of stack smashing, buffer overruns, etc, and plan a deployment accordingly.

Re: Gogs, an alternative to Gitlab

#215

Post by e12e » Tue, Mar 17, 2015, 3:57 AM UTC

pdenya wrote: post #192

hashtree wrote: post #174

Earlier quoted context omitted.

Simply personal preference. I'd like to use the same supporting tools, UI, zero context switching between products, etc. Funny enough, I use some of the social features (issues/milestones/wiki) for project management, even for my own projects.

Bitbucket provides those. I use it professionally because I like all my stuff in one place and that's where I keep my free private repos.

While bitbucket have some similar features to github (or vice-versa), the features are not the same. So if you want to use only one interface, and you prefer github for projects with multiple collaborators, bitbucket isn't really much of an alternative. Or, if you prefer bitbucket, but is also professionally involved in a number of projects hosted on github, you're still stuck with two interfaces (this is likely the case for pretty much everyone, as almost everyone will have a dependency of some kind hosted on github, and at one point or other you'll probably want to/have to deal with upstream).

This would be true even if bitbucket was (subjectively) better: assuming one values having one consistent interface more than the "best" interface.

I don't necessarily think github's interface(s) are better than bitbucket (or that either are good, for that matter) -- but I can certainly relate to the desire for having a consistent interface, to lower cognitive overhead.

For me, that's the main argument for using Free/Open solutions, that one can self-host: one can guarantee consistency, which in turn can save time. There'll always be a balance between how much time is needed for managing such solutions, and between stability and stagnation.

All that said, it's hard to deny that github managed to leverage the network effect much more dramatically than either self-hosted CVS, stand-alone bugzilla+wiki or Source Forge managed to do. (The latter probably because they didn't realize what they business model should have been: not ads, but charging for forge-services. Then again, AFAIK github isn't profitable, either, yet?).

Re: Gogs, an alternative to Gitlab

#216

Post by Vendan » Tue, Mar 17, 2015, 4:04 AM UTC

mholt wrote: post #212

Vendan wrote: post #207

Just as a warning, I don't consider gogs to be stable enough for production use. There's data race errors that pop up, resulting in errors resolving various assets. I've had everything from user's avatar icons to the main homepage randomly error out as 404. The dev doesn't seem to understand that data races, i.e. unsafe cross thread data access, is an issue. In addition, note that it and least some of the libraries i…

> note that it and least some of the libraries it uses are written by devs for whom english is at best a second language, so expect difficulties communicating Considering that English is not their native language, I'd say they're doing pretty darn well so far. Speaking with at least one of the developers personally and via email, I've never had any trouble. > don't expect assistance from the community Well that's a m…

I tried to get the developer to fix my issue, or even consider it as an issue, but got no where.

I'll admit, I don't speak for the community as a whole, but about every go developer I've spoken to has the same feeling I do, and it's echoed all over the web. Macaron, the central framework, is inspired by, and rather heavily follows, the style of Martini. It's dependency injection and runtime reflection code style is considered highly unsafe. But don't take my word for it, maybe you'll listen to the author of Martini? http://codegangsta.io/blog/2014/05/19/my-thoughts-on-martini... Or the post it's in response to? https://stephensearles.com/three-reasons-you-should-not-use-...

Re: Gogs, an alternative to Gitlab

#217

Post by e12e » Tue, Mar 17, 2015, 4:19 AM UTC

mrmondo wrote: post #204

sytse wrote: post #70

Hi, GitLab CEO here. Installing GitLab should take only 2 minutes with the Omnibus packages available on https://about.gitlab.com/downloads/ Upgrading GitLab is as simple as: sudo gitlab-ctl stop unicorn sudo gitlab-ctl stop sidekiq sudo gitlab-rake gitlab:backup:create sudo dpkg -i gitlab_x.x.x-omnibus.xxx.deb sudo gitlab-ctl reconfigure And we're working very hard to make sure this is a flawless, uneventful & borin…

+1 (Or can I give +1million?) to Gitlab. GitLab is now one of the core products in our business and we (Devs, Ops and PM's) love it. For Ops: * It's easy to deploy. * It's easy to manage / support. * Gitlab-CI now builds all our Docker images which is great. * Gitlab-CI runners are a pain in the ass to deploy. For Devs: * It's workflow and code review is great. * GitLab CI is a great alternative to using external CI…

Thank you for sharing your points: for me this is actually quite an endorsement of gogs (But then, I'm not looking for an alternative to gitlab).

> * There is no Debian package which would be nice.

True. AFAIK there aren't any packages in Debian that depend on go/golang yet, not even in sid. That doesn't mean one can't make out-of-band debs, of course, but gogs unfortunately isn't alone here. Does anyone know of any util/tool/package in go (other than golang) that's packaged for Debian?

> * It's written in a language that most Devs / Ops can't contribute to or bug fix.

As opposed to what? I'd think being able to patch something in go would be within the grasp of most Ops, and also most devs?

Re: Gogs, an alternative to Gitlab

#218

Post by sytse » Tue, Mar 17, 2015, 4:57 AM UTC

mrmondo wrote: post #204

sytse wrote: post #70

Hi, GitLab CEO here. Installing GitLab should take only 2 minutes with the Omnibus packages available on https://about.gitlab.com/downloads/ Upgrading GitLab is as simple as: sudo gitlab-ctl stop unicorn sudo gitlab-ctl stop sidekiq sudo gitlab-rake gitlab:backup:create sudo dpkg -i gitlab_x.x.x-omnibus.xxx.deb sudo gitlab-ctl reconfigure And we're working very hard to make sure this is a flawless, uneventful & borin…

+1 (Or can I give +1million?) to Gitlab. GitLab is now one of the core products in our business and we (Devs, Ops and PM's) love it. For Ops: * It's easy to deploy. * It's easy to manage / support. * Gitlab-CI now builds all our Docker images which is great. * Gitlab-CI runners are a pain in the ass to deploy. For Devs: * It's workflow and code review is great. * GitLab CI is a great alternative to using external CI…

Thanks mrmondo, glad to hear you like GitLab!

Re: Gogs, an alternative to Gitlab

#219

Post by sytse » Tue, Mar 17, 2015, 4:59 AM UTC

lorddoig wrote: post #200

sytse wrote: post #70

Hi, GitLab CEO here. Installing GitLab should take only 2 minutes with the Omnibus packages available on https://about.gitlab.com/downloads/ Upgrading GitLab is as simple as: sudo gitlab-ctl stop unicorn sudo gitlab-ctl stop sidekiq sudo gitlab-rake gitlab:backup:create sudo dpkg -i gitlab_x.x.x-omnibus.xxx.deb sudo gitlab-ctl reconfigure And we're working very hard to make sure this is a flawless, uneventful & borin…

I put GitLab on a personal server a week or two ago for some stuff, and I'm sorry to say it but the overwhelming takeaway from that experience was watching it hog memory and spawn what felt like a million processes which somehow lingered for days after un installation until I noticed them. This thing runs one process, idles at 0.0% CPU, and is blazing fast in <450MB memory - when all you want is a nice git GUI for a…

I'm sorry to hear you experienced stray processes. Did you use the Omnibus packages? Did you use gitlab-ctl stop?

Re: Gogs, an alternative to Gitlab

#220

Post by mrmondo » Tue, Mar 17, 2015, 5:28 AM UTC

e12e wrote: post #217

mrmondo wrote: post #204

Earlier quoted context omitted.

+1 (Or can I give +1million?) to Gitlab. GitLab is now one of the core products in our business and we (Devs, Ops and PM's) love it. For Ops: * It's easy to deploy. * It's easy to manage / support. * Gitlab-CI now builds all our Docker images which is great. * Gitlab-CI runners are a pain in the ass to deploy. For Devs: * It's workflow and code review is great. * GitLab CI is a great alternative to using external CI…

Thank you for sharing your points: for me this is actually quite an endorsement of gogs (But then, I'm not looking for an alternative to gitlab). > * There is no Debian package which would be nice. True. AFAIK there aren't any packages in Debian that depend on go/golang yet, not even in sid. That doesn't mean one can't make out-of-band debs, of course, but gogs unfortunately isn't alone here. Does anyone know of any…

For sure - it's got lots of promise and we are by no means bound to what we've bought into - we'll use whatever's best, at the moment that's Gitlab.

To clarify I didn't mean that it would be nice to have packages that are maintained by or in the default Debian repo - but an apt repo for the project would be nice.

I've found Go a pain to read and hack with - Ruby and Python however are a lot more readable and any of our ops or devs would feel confident in finding / reporting bugs in either.