this post was submitted on 20 Apr 2026
322 points (97.9% liked)

Selfhosted

56958 readers
2297 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

If you're like me, you probably need to update your image tag to this new major version. I'll probably wait for a minor release first.

top 49 comments
sorted by: hot top controversial new old
[–] prism@lemmy.dbzer0.com 51 points 3 days ago

Finally, repository specific access tokens were added! I was missing this feature from GitHub (fine-grained access tokens) and had resorted to making service accounts that had access to a single repo. Time to clean that up :)

[–] ozoned@piefed.social 31 points 3 days ago (2 children)
[–] quick_snail@feddit.nl 3 points 3 days ago

This is my prerequisite for switching from GitHub to Codeberg

[–] prenatal_confusion@feddit.org 3 points 3 days ago

Yeees! So much different repos i want to be able to commit and report to ...

[–] pound_heap@lemmy.dbzer0.com 6 points 2 days ago (2 children)

I'm happily running v11 LTS - I have enough to do besides dealing with breaking changes every 3 months.

[–] possiblylinux127@lemmy.zip 3 points 2 days ago (1 children)

v11 goes eol in 2 months

I genuinely don't understand your reasoning

[–] pound_heap@lemmy.dbzer0.com 7 points 2 days ago

Well, before your response, v11 was the latest LTS release, received security patches and did all I wanted it to do. Now, I actually did look at the new release and found out that 15 is a new LTS. So, thank you! I guess it's time to review the breaking changes and get prepared.

[–] ikidd@lemmy.world 1 points 2 days ago (1 children)

That is getting pretty far behind unless you're leaving yourself open to go back to Gitea. I think 12 was the hard fork.

[–] pound_heap@lemmy.dbzer0.com 2 points 2 days ago

I started from zero with Forgejo, so Gitea is not a consideration. I just don't need latest and greatest as long as security is covered. But I finally noticed that v15 is the new LTS, so that's what I hope to run during the next couple of years.

[–] northernlights@lemmy.today 24 points 3 days ago* (last edited 3 days ago) (1 children)

I very much have my eye on that. Pretty sure that's going to be my next self-host just because I love everything about it, not so much because I'll need it. Pleeeease federate. I know it's a whole lot of work, but it would be a significant net benefit to all developers worldwide who code because they like it.

[–] julianwgs@discuss.tchncs.de 5 points 3 days ago (1 children)

Donations will help them get there faster

[–] northernlights@lemmy.today 3 points 3 days ago (1 children)

I know, but I'll get on that after I find a job.

[–] julianwgs@discuss.tchncs.de 1 points 3 days ago

Sure, no worries. For me it was the same.

[–] badbytes@lemmy.world 24 points 3 days ago

An amazing project. Good work devs.

[–] chaospatterns@lemmy.world 16 points 3 days ago (1 children)

15.0 adds support for OIDC tokens being handed to Actions workflows compatible with GitHub Actions. I was excited to upgrade because I wanted to continue doing cosign Docker image signing, but then I found out that the Cosign transparency log doesn't support Forgejo. Looks like I need an alternative.

My next biggest problem is the Actions workflow itself. I setup Docker in Docker, but turns out there's a bit of work in preparing the runners to be on par with what I used on GitHub.

Otherwise, I've found Forgejo to be quite good and almost all my private repos are moved over.

[–] Miaou@jlai.lu 2 points 3 days ago

I tried to setup Forgejo CI but was turned off by the need to have nodejs installed to do anything, even cloning the repository. Does everyone just maintain their own images?

Gitlab CI by comparison will let me you any image (e.g. basic rustc imagé) and do the orchestration by itself. So much nicer to use imo

[–] iso@lemy.lol 12 points 4 days ago (2 children)

Forgejo's most promising feature was federation, and unfortunately, they don't seem to be working on that.

[–] tofu@lemmy.nocturnal.garden 47 points 3 days ago* (last edited 3 days ago) (3 children)
[–] MatSeFi@lemmy.liebeleu.de 23 points 3 days ago (1 children)

actually it is already meged and on v16.0 milestone list

[–] hoppolito@mander.xyz 7 points 3 days ago

That’s brilliant news!

I know this is still just very basic federation with mutual following of users, etc. - but having a working mvp implementation of this makes me really hopeful for the stepwise introduction of more and more federation goals to come to fruition.

[–] AcornTickler@sh.itjust.works 16 points 3 days ago (1 children)

Oh, didn't know Forgejo was ever intended to have federation. That's so cool!

[–] tofu@lemmy.nocturnal.garden 16 points 3 days ago

It's the main reason I choose them. Can't wait to open issues on other instances without creating an account and not everything being on GitHub.

[–] iso@lemy.lol 5 points 3 days ago
[–] RushLana@lemmy.blahaj.zone 10 points 3 days ago* (last edited 3 days ago)

Federation is worked on by forgefed if I remember right.

https://codeberg.org/ForgeFed/ForgeFed

[–] flubba86@lemmy.world 7 points 3 days ago (1 children)

Damn I feel like I only just upgraded to v14. Those guys develop fast.

It's noted in the release notes that they release a new major version every 3 months.

[–] XenoK@lemmy.dbzer0.com 4 points 3 days ago (5 children)

How does it compare to Gitea?

[–] purplemonkeymad@programming.dev 10 points 3 days ago (1 children)

Forked from gitea. The owners of the project implemented a change to the pr system where by you had the sign an agreement that the code belonged to them. This was seen as an intent to relisense at some point. Devs that wanted it to stay open moved to forgejo.

Until recently you could swap forgejo in to your gitea data, but now they are incompatible due to divergence.

[–] quick_snail@feddit.nl 0 points 3 days ago

Isn't that signing thing the legal way to keep things open source? Iirc FSF had that too.

[–] black_flag@lemmy.dbzer0.com 21 points 3 days ago

Forgejo is where the dev is happening now.

[–] cecilkorik@piefed.ca 13 points 3 days ago

Gitea is developed by a corporation. If you trust corporations not to enshittify eventually, maybe Gitea will be the exception to the rule, but I doubt it, for sufficiently long definitions of "eventually". Forgejo was forked specifically because the governance needed to be detached from the corporation, and that wasn't going to happen with Gitea. The community of open-source developers mostly voted with their feet. Forgejo is, in my humble opinion, going places. Gitea is not. Nothing specifically wrong with it, per se, but it doesn't really offer a sustainable development path forward I don't think.

[–] EncryptKeeper@lemmy.world 11 points 3 days ago

It’s a fork of Gitea with more extensive development.

I didn't notice a difference. Maybe if you start new then go forgejo but existing gitea I see no reason to move.

[–] GarboDog@lemmy.world 2 points 3 days ago (4 children)

This is the first time we’re hearing of this, what is Forgejo/ what’s it used for??

[–] Samiaouuu@jlai.lu 16 points 3 days ago (1 children)

Basically self hosted Github without microslop's bs

[–] GarboDog@lemmy.world 4 points 2 days ago

Ah nice! Will def keep this in mind when we eventually make a server ^^

[–] quick_snail@feddit.nl 8 points 3 days ago

It's the software that runs codeberg

[–] parzival@lemmy.org 4 points 3 days ago

Self hosted git server (github alt)

[–] Keelhaul@sh.itjust.works 2 points 2 days ago

Locally hosted git server (fork of Gitea)

[–] HairyHarry@lemmy.world 2 points 3 days ago (3 children)

Amy Idea why there isn't a ":latest" release?

[–] poVoq@slrpnk.net 16 points 3 days ago

Because you usually don't want to do automatic upgrades across major versions. There is a "latest" equivalent for each major version release though.

[–] ikidd@lemmy.world 7 points 3 days ago

It might be OK now, but for a while there before they hard forked, you set yourself up for issues if you updated majors without being aware of breaking changes.

[–] EncryptKeeper@lemmy.world 5 points 3 days ago* (last edited 3 days ago)

Forgejo was initially a soft fork of Gitea but they knew it would very possibly become a hard fork. Using the latest tag meant your setup could break unexpectedly so I think they’d opted to not use it at all. What you want to do is use the full version “15” in this case which will keep it updated up the currently major release.

[–] galaxy_nova@lemmy.world 1 points 3 days ago* (last edited 3 days ago) (2 children)

Thoughts on this versus tangled besides this being more mature? Also question, I have cloudflare serving as my ddns, I believe some settings I have configured there prevent ssh from working to my forgejo instance. Is it a security risk to allow ssh traffic properly? I have other services on the same subdomain published as well if that matters.

Edit: would Tailscale be a solution here?

[–] EncryptKeeper@lemmy.world 2 points 3 days ago

Tangled seems to focus on the “social” aspect by being inherently federated using the protocol Bluesky uses.

Federation is in the works for Forgejo but it’s not a focus.

[–] purplemonkeymad@programming.dev 1 points 3 days ago (1 children)

Recommendation would be that you want to set up your ssh so that it only accepts publickey authentication. You also want to make sure you are not using a proxied DNS value, as CF only proxies http requests.

Personally I didn't bother to setup ssh access as https typically works fine.

[–] galaxy_nova@lemmy.world 1 points 3 days ago

I setup ssh key access only on all my machines so that bit is ok. Maybe I’ll forgo ssh like you’re suggesting as well. I thought I had some use for it but it’s been a while since I was messing with my forgejo instance, I’ve kind of fallen back to GitHub and codeberg for a bit since I’ve been busy. I couldn’t get https cloning to work for some reason either so I neee to investigate that I guess.

[–] uuj8za@piefed.social 1 points 3 days ago

Yeah... I'm gonna wait for 15.1...

[–] Decronym@lemmy.decronym.xyz -2 points 3 days ago* (last edited 2 days ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
CF CloudFlare
DNS Domain Name Service/System
Git Popular version control system, primarily for code
LTS Long Term Support software version

4 acronyms in this thread; the most compressed thread commented on today has 15 acronyms.

[Thread #250 for this comm, first seen 21st Apr 2026, 14:00] [FAQ] [Full list] [Contact] [Source code]