35
submitted 1 year ago by freddo@feddit.nu to c/selfhosted@lemmy.world

Looking into possibly replacing my GitLab instance, as I find it bloated and heavy on both hardware and maintenance compared to alternatives.

Currently I'm looking at:

  • GitTea
  • Forgejo, as GitTea turned into a for-profit, otherwise that would be the clear choice
  • OneDev

So I'm wondering what the people on here use, and if they have any other suggestions or opinions?

top 26 comments
sorted by: hot top controversial new old
[-] haroldstork@lemm.ee 23 points 1 year ago

Gitea is light and fast so I highly recommend it. If you are worried about it being a for profit company, then use the fork, but if they haven’t done any harm, I’d said give them a shot.

[-] ripe_banana@lemmy.world 9 points 1 year ago

Are there any feature differences between gitea and forgejo?

I can't figure out any differences other than the ownership structure.

[-] Chaphasilor@feddit.nl 6 points 1 year ago

Forgejo is about to introduce support for federation, but is also planning to upstream those changes to GitTea down the line

[-] ripe_banana@lemmy.world 3 points 1 year ago

Federation would be super cool. Lemmy has really sold me on it.

[-] AbidanYre@lemmy.world 4 points 1 year ago

I tried it at one point and they hadn't even done a find/replace on "gitea", so it would seem the changes, if any, are pretty minimal.

[-] Dirk@lemmy.ml 8 points 1 year ago

+1 for Forgejo. It is super lightweight but still has all the common features. It also is not run by a for-profit corporation but is fully community-driven and maintained by a non-profit association everyone can become a member of.

[-] ShittyKopper 8 points 1 year ago

if you have a hard time choosing between Gitea and Forgejo I recommend picking Gitea for now, as they haven't done anything bad just yet, but if they do Forgejo supports migration from Gitea.

iirc there isn't an official way of migrating the other way so if Forgejo fucks up you may end up out of luck

[-] thedoginthewok@lemmy.world 8 points 1 year ago

What do you mean by "gitea turned into a for profit"?

I really like gitea, set it up at my last job and it was easy to work with and used very little resources.

[-] freddo@feddit.nu 4 points 1 year ago
[-] vegetaaaaaaa@lemmy.world 4 points 1 year ago* (last edited 1 year ago)

What do you mean by “gitea turned into a for profit”?

https://lemmy.world/comment/1377774 - it's FUD. Forgejo is also backed by a company, by the way [1]

[-] juri@lemmy.world 5 points 1 year ago

I’m on https://github.com/charmbracelet/soft-serve and like it very much. It couldn’t be any simpler. As long as you don’t need PR/MR features and full blown web UI it’s a really good choice IMHO.

[-] freddo@feddit.nu 1 points 1 year ago

Certainly looks interesting, though being able to do code review and a more full-fledged CI/CD solution is a requirement.

[-] thelastknowngod@lemm.ee 1 points 1 year ago

I think the idea with soft serve us that you use hooks and use a dedicated ci/cd tool. I use adnanh/webhook for lightweight ci/cd on personal projects.

[-] leraje@lemmy.world 3 points 1 year ago

Big fan of Gogs personally. Simple, light and a doddle to install.

[-] exu@feditown.com 2 points 1 year ago

Gitea is a fork of Gogs

[-] eleitl@lemmy.world 3 points 1 year ago

Are the alternatives feature-complete in regards to GitLab CE?

[-] johntash@eviltoast.org 3 points 1 year ago

Do you need ci/cd or only git? If just git, gitea or forgejo are super simple.

If you don't need multiple users or a web ui, you could also just use ssh and store git repos on a server somewhere without extra services running:

https://git-scm.com/book/en/v2/Git-on-the-Server-Setting-Up-the-Server

[-] jsnfwlr@lemmy.world 1 points 1 year ago

since 1.19 Gitea supports CI/CD action runners that are compatible with github actions. I have one that generates a static site from the data I store in gitea and publishes it to netlify.

[-] freddo@feddit.nu 1 points 1 year ago

CI/CD, multiple users, container registry, and a web UI are requirements, though not much more which is why I find GitLab to be a bit over the top.

[-] PupBiru@kbin.social 1 points 1 year ago* (last edited 1 year ago)

so i just did a quick search and apparently

Starting with Gitea 1.19, Gitea Actions are available as a built-in CI/CD solution.

*edited:

also they support being a package repo, including container registry

[-] cow@lemmy.world 2 points 1 year ago

Maybe sourcehut if you need more than git hosting.

[-] exu@feditown.com 2 points 1 year ago

I'm using Gitea. I did try OneDev and it is very nice, but mainly intended for single-team usage as it doesn't use different namespaces for user projects. It's also very much its own thing, with its own CI/CD for example. Gitea can integrate with other projects much better, like using Woodpecker for CI/CD or logging in with GitHub/GitLab using Oauth.

I did follow the drama around Gitea/Forgejo, but for now the Gitea company hasn't done anything wrong, there's no feature difference (Forgejo aims to be a soft-fork for the moment) and Forgejo had a bit of drama around the lead developer ~1 month after it was founded.

[-] kreateer@programming.dev 2 points 1 year ago

I assume that by now you've made a decision, so if I may I'd like to chip in and ask what's the benefit of self-hosting a Git instance, like the ones mentioned, over using existing free services like GitHub or Codeberg to host your code? What do you gain by hosting this yourself, apart from privacy and security?

[-] freddo@feddit.nu 2 points 1 year ago

I'd say the main benefit gained is sovereignty and a sense of place. This is not for personal use, but rather for a computer enthusiast association that I'm part of, so having our own git to integrate with the rest of our services makes sense. Throw on branding and link it to our SSO.

[-] pnutzh4x0r@lemmy.world 2 points 1 year ago

My friend has deployed Phorge for himself and appears to be happy with it.

load more comments
view more: next ›
this post was submitted on 27 Jul 2023
35 points (100.0% liked)

Selfhosted

39980 readers
445 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS