5 ms·

I was a Gitlab fan, until I tried Gitea. I wish they'd start shrinking Gitlab image sizes quite a bit.

by vkaku 8y ago

storrgie 8y ago
self hosting gitlab feels completely untenable, gitea is a wonderful project.
- lordelph 8y ago
  Honestly, it's painless. Fire up a cloud server, run the omnibus installer and you're away. I can't remember having any serious issues in five years running it that way.
  - mikewhy 8y ago
    Ditto. Ran the Docker version for years. Upgrading was as simple as changing a version number and restarting.
ausjke 8y ago
very true, running gitea myself for 2 years, easy to use, light-weight(one go binary to run, one minute painless upgrade with new releases), no memory/cpu pressure whatsoever(I host linux kernel tree myself, so yes large git is fine there too).
emilycook 8y ago
Hi! Thanks for the feedback. We'd love to be as lightweight as Gitea, but our end goal of being a single application for the entire DevOps lifecycle means that we are naturally more complicated. We are always working toward improving our resource usage though! You can see our issues around performance here: https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=performance https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...
h1d 8y ago
Lightweight and it's simple for non devs to pick up the interface as well, using it across multiple companies, zero complaints.
chewmieser 8y ago
Saying Gitea is better because it's lighter weight is like saying a moped is better then an SUV because it's lighter weight. Gitea / Gogs is great for personal projects and small teams that don't need all the CI/devops/scrum/etc features that GitLab provides, but they're not really in the same ballpark. GitLab is definitely resource hungry, but we self-host it for under $100/mo on AWS. This includes the cost of the CI infrastructure as well - EC2 instances being spawned by the multi-runner with docker+executor for each unique pipeline running. Management of the server has been as easy as logging into the GitLab server periodically and running a yum update... It's never gone down.
- tagrun 8y ago
  Gitlab didn't have those extra features at early stages either (Gitea does have CI API BTW, if not a built-in CI). And Gitea doesn't have Gitlab's financial resources. But the point being made is orthogonal to the feature set: Gitlab (mostly written in Ruby) isn't using hardware resources (memory, CPU cycles, parallelism) as efficiently as Gitea (written in Go) does. This is well reflected to the minimal system requirements, even when you aren't using any of those additional features: https://docs.gitlab.com/ee/install/requirements.html https://docs.gitlab.com/ee/install/requirements.html whereas you can in principle use Gitea even on a Raspberry Pi Zero for a small group. For example, disregarding parallelism and wasted CPU cycles and just looking at memory usage: I have a running instance and its using 30MBs of RAM at the moment (~10 users, ~100 repos). If I move all the repos, issues, PRs to a Gitlab instance, I would be looking at GBs according to their minimal requirements. This is related to the mindset in which memory and CPU are considered as infinite resources.
velcrovan 8y ago
And I was a Gitea fan until I tried Fossil! Very different development style than Git, but for my personal projects I really like it.
- jessermeyer 8y ago
  How do you find Fossil works with large binary files (assuming you've tried)?
  - velcrovan 8y ago
    I have never found a good reason to use a source control system on stuff that isn't source code.
tracker1 8y ago
If you don't need what gitlab/github or for that matter Azure Devops, offers... using bare remote repos over SSH+FS might just be a better approach. All you need is an SSH server with file system access behind it.

I was a Gitlab fan, until I tried Gitea. I wish they'd start shrinking Gitlab image sizes quite a bit.

by vkaku 8y ago

I was a Gitlab fan, until I tried Gitea. I wish they'd start shrinking Gitlab image sizes quite a bit.

storrgie 8y ago

self hosting gitlab feels completely untenable, gitea is a wonderful project.

lordelph 8y ago
Honestly, it's painless. Fire up a cloud server, run the omnibus installer and you're away. I can't remember having any serious issues in five years running it that way.
- mikewhy 8y ago
  Ditto. Ran the Docker version for years. Upgrading was as simple as changing a version number and restarting.

ausjke 8y ago

very true, running gitea myself for 2 years, easy to use, light-weight(one go binary to run, one minute painless upgrade with new releases), no memory/cpu pressure whatsoever(I host linux kernel tree myself, so yes large git is fine there too).

emilycook 8y ago

Hi! Thanks for the feedback. We'd love to be as lightweight as Gitea, but our end goal of being a single application for the entire DevOps lifecycle means that we are naturally more complicated. We are always working toward improving our resource usage though! You can see our issues around performance here: https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=performance https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...

h1d 8y ago

Lightweight and it's simple for non devs to pick up the interface as well, using it across multiple companies, zero complaints.

chewmieser 8y ago

Saying Gitea is better because it's lighter weight is like saying a moped is better then an SUV because it's lighter weight. Gitea / Gogs is great for personal projects and small teams that don't need all the CI/devops/scrum/etc features that GitLab provides, but they're not really in the same ballpark. GitLab is definitely resource hungry, but we self-host it for under $100/mo on AWS. This includes the cost of the CI infrastructure as well - EC2 instances being spawned by the multi-runner with docker+executor for each unique pipeline running. Management of the server has been as easy as logging into the GitLab server periodically and running a yum update... It's never gone down.

tagrun 8y ago
Gitlab didn't have those extra features at early stages either (Gitea does have CI API BTW, if not a built-in CI). And Gitea doesn't have Gitlab's financial resources. But the point being made is orthogonal to the feature set: Gitlab (mostly written in Ruby) isn't using hardware resources (memory, CPU cycles, parallelism) as efficiently as Gitea (written in Go) does. This is well reflected to the minimal system requirements, even when you aren't using any of those additional features: https://docs.gitlab.com/ee/install/requirements.html https://docs.gitlab.com/ee/install/requirements.html whereas you can in principle use Gitea even on a Raspberry Pi Zero for a small group. For example, disregarding parallelism and wasted CPU cycles and just looking at memory usage: I have a running instance and its using 30MBs of RAM at the moment (~10 users, ~100 repos). If I move all the repos, issues, PRs to a Gitlab instance, I would be looking at GBs according to their minimal requirements. This is related to the mindset in which memory and CPU are considered as infinite resources.

velcrovan 8y ago

And I was a Gitea fan until I tried Fossil! Very different development style than Git, but for my personal projects I really like it.

jessermeyer 8y ago
How do you find Fossil works with large binary files (assuming you've tried)?
- velcrovan 8y ago
  I have never found a good reason to use a source control system on stuff that isn't source code.

tracker1 8y ago

If you don't need what gitlab/github or for that matter Azure Devops, offers... using bare remote repos over SSH+FS might just be a better approach. All you need is an SSH server with file system access behind it.