6 ms·

Gogs – A simple, stable and extensible self-hosted Git service

101 points by jcamou 8y ago

frfl 8y ago
https://gitea.io/en-us/ https://gitea.io/en-us/ is a fork with some additional functionality and more open to outside contribution[1] [1] https://blog.gitea.io/2016/12/welcome-to-gitea/ https://blog.gitea.io/2016/12/welcome-to-gitea/
- Hello71 8y ago
  previously: https://news.ycombinator.com/item?id=17006848 https://news.ycombinator.com/item?id=17006848 tl;dr "additional functionality" yes, and also some missing functionality.
  - spacebearmakes 8y ago
    Except Gitea has all the functionality in the list you linked.
- Master_Odin 8y ago
  Yeah, it was disappointing to see that the author of Gogs considers stuff like deleting branches and doing squash and merges outside the scope of what Gogs should do. Much happier after moving to Gitea.
  - black-tea 8y ago
    That's great imo. I strongly dislike these things being much more than "viewers" for the underlying git repo. Deleting branches and especially merging and squashing should be done with git. Double especially squashing... I hate to think of the mess that could cause when attempting it with a Web frontend.
    - elcomet 8y ago
      It's just git underneath.. And it's not going to do any mess. If it cannot perform an operation (like merging with conflicts), then it is going to tell you about it and you have to do it manually. But why restrict such functionalities that are very convenient ? I don't think that `git push --delete <remote_name> <branch_name>` is very easy to remember so I prefer doing it via the web interface.
- Sammi 8y ago
  Compare this years git activity of Gogs and Gitea: https://github.com/gogs/gogs/graphs/contributors?from=2018-01-01&to=2018-11-10&type=c https://github.com/gogs/gogs/graphs/contributors?from=2018-0... https://github.com/go-gitea/gitea/graphs/contributors?from=2018-01-01&to=2018-11-11&type=c https://github.com/go-gitea/gitea/graphs/contributors?from=2... Gogs is a one man show that accepts occasional drive by commits, while Gitea has several active maintainers and a lot of smaller contributers.
riffic 8y ago
Some people, when confronted with a problem, think "I know, I'll self-host a service." Now they have two problems.
- Xylakant 8y ago
  There’s variety of reasons to self-host. Having in internal git service can be nice if your connectivity is bad or spotty. An extreme case of that would be an airgapped network. Company policy might require that code does not leave the company network. You might legal be compelled to have full control over your code and where it goes (think: code under export restrictions). All of these people self-host and it solves a problem for them.
  - geezerjay 8y ago
    > There’s variety of reasons to self-host. Having in internal git service can be nice if your connectivity is bad or spotty. It's also hard to justify routing traffic through different continents if all you want to do is share a repository with someone sitting at a desk right next to you.
  - dijit 8y ago
    I think it also comes down to the availability of service or even not agreeing about the future of your hosting provider. Prime example is obviously github, why would my company host on github if they never made profit? that service could go away any time or the service could change in a way that is a pain for my company to migrate. It swings for other things you'd host, if I use services on Azure (such as Thunderhead) and I'm developing games, well Microsoft also develops games. I put my IP at risk.
- sigi45 8y ago
  I was working on a project which uses github.com. I never knew before how often github is actually down. A business is often enough to spend that extra cash to be independend from a thirdparty. The risk of not being able to deploy anything, because github is down, is real.
INTPenis 8y ago
How is it painless? I've been using gitlab since v7 and looking at the install instructions of gogs remind me of gitlab a lot. I recently got rid of my personal gitlab because it's too painful to operate. I only need a simple ssh user with a directory for my own purposes. Gitlab is only necessary at work where we are an entire team using it.
- pmoriarty 8y ago
  What made it so painful?
  - dijit 8y ago
    Gitlab? gitlab is quite painful. the guides hide the complexity because if you're able to get away with omnibus installation (or, docker installation) then you're going to be fine.. (unless it breaks, which to gitlabs credit, it doesn't). But as soon as you start touching HA, you have to unbuckle all of it's components, and that's where it becomes a real, real pain. Because gitlab does not assume you will do this and starts _freaking_ out when it tries to start something which doesn't exist on the local system. It takes a long time to find all the dials and triggers to turn local starting off, and even then you basically have a full omnibus installation sitting on each of your nodes, because even if features are turned off they sometimes need some part of the code for the feature. At this point upgrading anything is not just a tedious process, it's also error-prone and time consuming. Take every web-node down, upgrade the local packages on the web node you use to upgrade the database, then do the db migrations, then you go around upgrading everything else to the latest version, then you can slowly bring everything online and hope that it works. Don't event get me started on extending it's authentication system.
    - matteeyah 8y ago
      FWIW GitLab HA has improved a lot recently - see https://about.gitlab.com/solutions/high-availability/ https://about.gitlab.com/solutions/high-availability/ for an overview You can open issues about specific complaints in [1] and [2]. [1] - https://gitlab.com/gitlab-org/gitlab-ce https://gitlab.com/gitlab-org/gitlab-ce [2] - https://gitlab.com/gitlab-org/omnibus-gitlab https://gitlab.com/gitlab-org/omnibus-gitlab
johnchristopher 8y ago
I understand we could change the repo explorer functionnality since it's based on GIT but why keep the issues and wiki tied to this GIT service ? Why don't we have independent issues management, GIT stuff and wiki solutions that could be plugged into a webpage with basic URL support to link between git updates and bug reports ?
floren 8y ago
The truly painful thing about using gogs has been the inability to search issues. Maddening once you get past a trivial number of issues and just want to know if someone's reported a bug.
- CyberShadow 8y ago
  According to https://docs.gitea.io/en-us/comparison/ https://docs.gitea.io/en-us/comparison/ , it looks like this is implemented in the Gitea fork.
  - rcarmo 8y ago
    It is. I run it for some personal projects and it does search issues.
okket 8y ago
Previous discussion from 2 1/2 years ago: https://news.ycombinator.com/item?id=11374003 https://news.ycombinator.com/item?id=11374003 (183 comments) Full list of discussions about Gogs: https://hn.algolia.com/?query=gogs&sort=byPopularity&prefix&page=0&dateRange=all&type=story https://hn.algolia.com/?query=gogs&sort=byPopularity&prefix&...
nwmcsween 8y ago
IMO both of these are the wrong way to go about having a git web ui, a simple hook could generate html partials and with a bit of javascript stream the fragments when required. Bugs/todos should also be under source control and would be handled better again by a hook.

101 points by jcamou 8y ago

frfl 8y ago

https://gitea.io/en-us/ https://gitea.io/en-us/ is a fork with some additional functionality and more open to outside contribution[1] [1] https://blog.gitea.io/2016/12/welcome-to-gitea/ https://blog.gitea.io/2016/12/welcome-to-gitea/

Hello71 8y ago
previously: https://news.ycombinator.com/item?id=17006848 https://news.ycombinator.com/item?id=17006848 tl;dr "additional functionality" yes, and also some missing functionality.
- spacebearmakes 8y ago
  Except Gitea has all the functionality in the list you linked.
Master_Odin 8y ago
Yeah, it was disappointing to see that the author of Gogs considers stuff like deleting branches and doing squash and merges outside the scope of what Gogs should do. Much happier after moving to Gitea.
- black-tea 8y ago
  That's great imo. I strongly dislike these things being much more than "viewers" for the underlying git repo. Deleting branches and especially merging and squashing should be done with git. Double especially squashing... I hate to think of the mess that could cause when attempting it with a Web frontend.
  - elcomet 8y ago
    It's just git underneath.. And it's not going to do any mess. If it cannot perform an operation (like merging with conflicts), then it is going to tell you about it and you have to do it manually. But why restrict such functionalities that are very convenient ? I don't think that `git push --delete <remote_name> <branch_name>` is very easy to remember so I prefer doing it via the web interface.
Sammi 8y ago
Compare this years git activity of Gogs and Gitea: https://github.com/gogs/gogs/graphs/contributors?from=2018-01-01&to=2018-11-10&type=c https://github.com/gogs/gogs/graphs/contributors?from=2018-0... https://github.com/go-gitea/gitea/graphs/contributors?from=2018-01-01&to=2018-11-11&type=c https://github.com/go-gitea/gitea/graphs/contributors?from=2... Gogs is a one man show that accepts occasional drive by commits, while Gitea has several active maintainers and a lot of smaller contributers.

riffic 8y ago

Some people, when confronted with a problem, think "I know, I'll self-host a service." Now they have two problems.

Xylakant 8y ago
There’s variety of reasons to self-host. Having in internal git service can be nice if your connectivity is bad or spotty. An extreme case of that would be an airgapped network. Company policy might require that code does not leave the company network. You might legal be compelled to have full control over your code and where it goes (think: code under export restrictions). All of these people self-host and it solves a problem for them.
- geezerjay 8y ago
  > There’s variety of reasons to self-host. Having in internal git service can be nice if your connectivity is bad or spotty. It's also hard to justify routing traffic through different continents if all you want to do is share a repository with someone sitting at a desk right next to you.
- dijit 8y ago
  I think it also comes down to the availability of service or even not agreeing about the future of your hosting provider. Prime example is obviously github, why would my company host on github if they never made profit? that service could go away any time or the service could change in a way that is a pain for my company to migrate. It swings for other things you'd host, if I use services on Azure (such as Thunderhead) and I'm developing games, well Microsoft also develops games. I put my IP at risk.
sigi45 8y ago
I was working on a project which uses github.com. I never knew before how often github is actually down. A business is often enough to spend that extra cash to be independend from a thirdparty. The risk of not being able to deploy anything, because github is down, is real.

INTPenis 8y ago

How is it painless? I've been using gitlab since v7 and looking at the install instructions of gogs remind me of gitlab a lot. I recently got rid of my personal gitlab because it's too painful to operate. I only need a simple ssh user with a directory for my own purposes. Gitlab is only necessary at work where we are an entire team using it.

pmoriarty 8y ago
What made it so painful?
- dijit 8y ago
  Gitlab? gitlab is quite painful. the guides hide the complexity because if you're able to get away with omnibus installation (or, docker installation) then you're going to be fine.. (unless it breaks, which to gitlabs credit, it doesn't). But as soon as you start touching HA, you have to unbuckle all of it's components, and that's where it becomes a real, real pain. Because gitlab does not assume you will do this and starts _freaking_ out when it tries to start something which doesn't exist on the local system. It takes a long time to find all the dials and triggers to turn local starting off, and even then you basically have a full omnibus installation sitting on each of your nodes, because even if features are turned off they sometimes need some part of the code for the feature. At this point upgrading anything is not just a tedious process, it's also error-prone and time consuming. Take every web-node down, upgrade the local packages on the web node you use to upgrade the database, then do the db migrations, then you go around upgrading everything else to the latest version, then you can slowly bring everything online and hope that it works. Don't event get me started on extending it's authentication system.
  - matteeyah 8y ago
    FWIW GitLab HA has improved a lot recently - see https://about.gitlab.com/solutions/high-availability/ https://about.gitlab.com/solutions/high-availability/ for an overview You can open issues about specific complaints in [1] and [2]. [1] - https://gitlab.com/gitlab-org/gitlab-ce https://gitlab.com/gitlab-org/gitlab-ce [2] - https://gitlab.com/gitlab-org/omnibus-gitlab https://gitlab.com/gitlab-org/omnibus-gitlab

johnchristopher 8y ago

I understand we could change the repo explorer functionnality since it's based on GIT but why keep the issues and wiki tied to this GIT service ? Why don't we have independent issues management, GIT stuff and wiki solutions that could be plugged into a webpage with basic URL support to link between git updates and bug reports ?

floren 8y ago

The truly painful thing about using gogs has been the inability to search issues. Maddening once you get past a trivial number of issues and just want to know if someone's reported a bug.

CyberShadow 8y ago
According to https://docs.gitea.io/en-us/comparison/ https://docs.gitea.io/en-us/comparison/ , it looks like this is implemented in the Gitea fork.
- rcarmo 8y ago
  It is. I run it for some personal projects and it does search issues.

okket 8y ago

Previous discussion from 2 1/2 years ago: https://news.ycombinator.com/item?id=11374003 https://news.ycombinator.com/item?id=11374003 (183 comments) Full list of discussions about Gogs: https://hn.algolia.com/?query=gogs&sort=byPopularity&prefix&page=0&dateRange=all&type=story https://hn.algolia.com/?query=gogs&sort=byPopularity&prefix&...

nwmcsween 8y ago

IMO both of these are the wrong way to go about having a git web ui, a simple hook could generate html partials and with a bit of javascript stream the fragments when required. Bugs/todos should also be under source control and would be handled better again by a hook.