66
submitted 6 days ago* (last edited 6 days ago) by Charger8232@lemmy.ml to c/selfhosted@lemmy.world

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.

top 29 comments
sorted by: hot top controversial new old
[-] MysteriousSophon21@lemmy.world 1 points 5 hours ago

+1 for Forgejo here. It's lightweight on resources compared to GitLab but still has all the features you'd need, plus the security/privacy focus aligns with your priorities. I've been running it on a small VPS for over a year and it's been rock soild.

[-] thirdBreakfast@lemmy.world 40 points 6 days ago

Forgejo - actively developed open source. It's what powers Codeberg. Easy to set up and manage with Docker. I moved to it from Gogs and skipped Gitea after reading about the forks.

[-] flubba86@lemmy.world 26 points 6 days ago

+1 for Forgejo

[-] possiblylinux127@lemmy.zip 13 points 5 days ago

Yup, it's pretty easy to set up, and since its runners are basically ripped from GitHub, you can piggy back of that documentation.

[-] AbidanYre@lemmy.world 27 points 6 days ago

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 21 points 6 days ago

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 5 days ago

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

[-] marcos@lemmy.world 3 points 6 days ago

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 6 days ago

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

[-] WhyJiffie@sh.itjust.works 2 points 5 days ago

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

[-] marcos@lemmy.world 1 points 5 days ago

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 5 days 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?

[-] johntash@eviltoast.org 6 points 4 days ago

I'm currently using forgejo and have no complaints.

Depending on your requirements, you might also consider just using regular git and ssh on a central server somewhere.

[-] NebulaNymph@programming.dev 22 points 6 days ago

+1 for Forgejo!

Just set it up with Docker this past week, it was fairly straightforward and has been working well since

[-] fmstrat@lemmy.nowsci.com 12 points 5 days ago* (last edited 5 days ago)

You asked for a service, but listed software. The latest FOSS software option is Forgejo, you should use it instead of others for all the reasons mentioned. However, if you're looking for a service, Codeberg runs a very popular Forgejo instance as a service.

[-] StrawberryPigtails@lemmy.sdf.org 18 points 6 days ago

I use Forgejo for my private git repos but in all honesty, it's massive overkill for my needs.

[-] darkan15@lemmy.world 15 points 6 days ago

Used Gitea for a while, and decided to switch to Forgejo before the hard fork split (no more code from Gitea), been using it since, In my opinion both work well, but prefer Forgejo.

[-] tal@lemmy.today 15 points 6 days ago

The things you're describing aren't really version control systems themselves. Git is a version control system; these are an ecosystem of web-based tools surrounding that version control system.

I don't know if there's a good term for these.

kagis

Wikipedia calls them "forges":

https://en.wikipedia.org/wiki/Forge_(software)

In free and open-source software (FOSS) development communities, a forge is a web-based collaborative software platform for both developing and sharing computer applications.

For software developers it is an online service to host the tools they need to work and communicate with their coworkers. It provides a workflow to propose modifications and engage in discussions. The goal is to reach an agreement that will allow these modifications to be merged into the software repository.

For users, a forge is a repository of computer applications, a place where bugs can be reported, a channel to be informed of security issues, etc.

The source code itself is stored in a revision control system and linked to a wide range of services such as a code review, bug database, continuous integration, etc. When a development community forks, it duplicates the content of the forge and is then able to modify it without asking permission. A community may rely on services scattered on multiple forges: they are not necessarily hosted under the same domain.

[-] whatwhatwhatwhat@lemmy.world 6 points 6 days ago

Sorry for the off-topic question, but this has been driving me crazy.

Is “kagis” the verb for using the search engine “kagi”? For the longest time I’ve been interpreting it as a “dejected sigh” emotional expression.

[-] tal@lemmy.today 7 points 6 days ago
[-] Charger8232@lemmy.ml 4 points 6 days ago

I guess it would be more akin to a "source code hosting service," but that would imply that I intend to open it to the internet (which isn't necessarily the case).

[-] Kwiuu@lemmy.world 2 points 4 days ago

Not what you want probably but Tangled.sh

tightly-knit
social coding. tangled is new social-enabled git collaboration platform built on atproto. we envision a place where developers have complete ownership of their code, open source communities can freely self-govern and most importantly, coding can be social and fun again.

[-] mvirts@lemmy.world 6 points 6 days ago

My only input is gitlab is very complicated, never used the others

[-] shiftymccool@programming.dev 4 points 6 days ago

I use Forgejo mostly for code archiving but anything that requires CI/CD, like personal code projects, i use OneDev. No extra setup for pipeline, batteries included

[-] 56_@lemmy.ml 4 points 6 days ago* (last edited 6 days ago)

Those 3 are all fairly similar. Here are some others I can think of:

  • Gitlab: many features, complex, pr workflow.
  • Forgejo / Gogs: simpler, github inspired interface, pr workflow.
  • Radicle: peer to peer, idk much more...
  • Sourcehut: minimal (non-github) interface, very modular, email workflow.
  • Cgit / Gitweb / etc.: just a git interface, no specific workflow.

 

If you're not using any of the additional features, cgit should be enough. If you're planning on collaborating with others, probably Forgejo would be better.

You can also use individual components of sourcehut, if you want a git web interface with just issue tracking, ci, or wiki, for example.

[-] sun@slrpnk.net 4 points 6 days ago

A pro of Sourcehut is that EVERYTHING can be done by email. So, if you use their issue tracker and want other people to be able to submit issues, they can do it without making an account.

[-] sxan@midwest.social 3 points 5 days ago

Sourcehut also supports Mercurial, so you also have an option to the herd mentality.

Sourcehut also has zero, or almost zero, JavaScript in the interface, so it doesn't suck

Sourcehut is also componentized, so you can mix and match the pieces you want or need:

  • VCS hosting
  • masking list management
  • issue management
  • build server
  • man server

Sourcehut is by far the best hosted VCS option at the moment. The Mercurial support alone puts it miles ahead of the others, which are all hobbled by tight coupling to git.

[-] DragonBard@ttrpg.network 3 points 5 days ago

If you are not wed to git, and are willing to try something else, why not give Fossil SCM a try. It's created and maintained by the creator of SQLite. It's a single executable that provides everything for modern source code management, including a website, and even has an official docker file that just works.

Issue tracking, forum support, email, it's all there, in a single executable that can serve as both the front and back end depending on how you launch it. And it's a smaller install than git by itself.

this post was submitted on 27 Jul 2025
66 points (100.0% liked)

Selfhosted

50026 readers
312 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 2 years ago
MODERATORS