this post was submitted on 27 Jul 2025
68 points (98.6% liked)

Selfhosted

60542 readers
687 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
68
Recommendations for a source code hosting service (lemmy.ml)
submitted 11 months ago* (last edited 11 months ago) by Charger8232@lemmy.ml to c/selfhosted@lemmy.world
42 comments fedilink hide all child comments
 

I am looking for recommendations for an open source self-hosted ~~version control system~~ source code hosting service. I found a few, but I can't decide on which one to pick:

If there's a better one than the ones I've listed here, I'd love to hear about it!

I care primarily about privacy and security, if that makes any difference.

you are viewing a single comment's thread
view the rest of the comments
[–] AbidanYre@lemmy.world 29 points 11 months ago (2 children)

Gogs is the original. Gitea is a fork because the dev of Gogs wasn't taking community input (I think that was the reasoning behind it). Forgejo is a fork of gitea because some folks didn't like gitea forming a for profit corporation (Or something to that effect).

As far as day to day use they're all fairly similar, though it's been a long time since I used Gogs.

[–] princessnorah@lemmy.blahaj.zone 21 points 11 months ago (1 children)

It's not just the for-profit corporation, there's also governance issues. Basically, the community elected certain positions and then had the rug pulled out from them such that no elections would be held again.

In the name of the Gitea Community who elected you last year, we welcome the creation of a for-profit company that allows you to make a living out of Gitea.

[...]

We believed you when you promised to pass along the ownership of the Gitea project to your elected successors. This promise is part of an essential bond between you and the strong Community of volunteers, as well as all those who rely upon our collective efforts.

With that in mind, you can understand our surprise when we learned on October 25th, 2022 that both the domains and the trademark were transferred to a for-profit company without our knowledge or approval.

Source.

[–] AbidanYre@lemmy.world 4 points 11 months ago

Thanks, I knew there was a bit more to it but hadn't followed it all that closely.

[–] marcos@lemmy.world 3 points 11 months ago (2 children)

IMO, the Gogs dev was correct. If you look at that community input and what Gitea became, I was glad to use the version that rejected it.

But I don't know how it compares with Forgejo.

[–] _cryptagion@quokk.au 8 points 11 months ago

It’s Gitea with some security fixes and community input, as open source software should be.

[–] WhyJiffie@sh.itjust.works 2 points 11 months ago (1 children)

what's the problem with gitea? I never used gogs so I can't compare it

[–] marcos@lemmy.world 1 points 11 months ago (1 children)

The added features made it harder to deploy, came with some bugs, and overall traded a simple design for community-oriented features that IMO were a negative value overall.

[–] WhyJiffie@sh.itjust.works 2 points 11 months ago

made it harder to deploy? Isn't it still just a single binary, a config file and a directory for data?

bugs are inevitable for evolving software.

which community oriented features do you mean? are they in the way, or is it just that you don't need them?