#gitea — Public Fediverse posts

GitHub Actions lock-in is why developers won't switch to Gitea or Forgejo despite record outages

#forgejo #git #gitea #github #microsoft #scm

https://www.makeuseof.com/github-keeps-breaking-and-almost-no-one-is-leaving-the-reason-is-one-feature/

If anybody self-host their #Git repositories via #forgejo #gitea etc, and taking any measures to protect your site from #AI crawlers.

How are you doing it? What are the options?

Thanks

Thank you, everyone. GitNex just crossed 800 stars on Codeberg. This is a great achievement for the project.

Have a great weekend!

#gitnex #app #git #android #codeberg #gitea #forgejo #foss #opensource

Thank you, everyone. GitNex just crossed 800 stars on Codeberg. This is a great achievement for the project.

Have a great weekend!

#gitnex #app #git #android #codeberg #gitea #forgejo #foss #opensource

Oh... #codeberg down with error: `504 Gateway Time-out. The server didn't respond in time.`

Update: It's now error 500 Internal server error. Forgejo version: 15.0.0-108-6d221141+gitea-1.22.0

https://status.codeberg.org/status/codeberg

https://social.anoxinon.de/@Codeberg
https://social.anoxinon.de/@codebergstatus

I was just about to init a new repo and start pushing some files!

#git #repo #forgejo #error504 #gitea #error500

Oh... #codeberg down with error: `504 Gateway Time-out. The server didn't respond in time.`

Update: It's now error 500 Internal server error. Forgejo version: 15.0.0-108-6d221141+gitea-1.22.0

https://status.codeberg.org/status/codeberg

https://social.anoxinon.de/@Codeberg
https://social.anoxinon.de/@codebergstatus

I was just about to init a new repo and start pushing some files!

#git #repo #forgejo #error504 #gitea #error500

Oh... #codeberg down with error: `504 Gateway Time-out. The server didn't respond in time.`

Update: It's now error 500 Internal server error. Forgejo version: 15.0.0-108-6d221141+gitea-1.22.0

https://status.codeberg.org/status/codeberg

https://social.anoxinon.de/@Codeberg
https://social.anoxinon.de/@codebergstatus

I was just about to init a new repo and start pushing some files!

#git #repo #forgejo #error504 #gitea #error500

Oh... #codeberg down with error: `504 Gateway Time-out. The server didn't respond in time.`

Update: It's now error 500 Internal server error. Forgejo version: 15.0.0-108-6d221141+gitea-1.22.0

https://status.codeberg.org/status/codeberg

https://social.anoxinon.de/@Codeberg
https://social.anoxinon.de/@codebergstatus

I was just about to init a new repo and start pushing some files!

#git #repo #forgejo #error504 #gitea #error500

Oh... #codeberg down with error: `504 Gateway Time-out. The server didn't respond in time.`

Update: It's now error 500 Internal server error. Forgejo version: 15.0.0-108-6d221141+gitea-1.22.0

https://status.codeberg.org/status/codeberg

https://social.anoxinon.de/@Codeberg
https://social.anoxinon.de/@codebergstatus

I was just about to init a new repo and start pushing some files!

#git #repo #forgejo #error504 #gitea #error500

Also, I enabled guest access to my #Gitea instance again, so anyone can browse my public projects, mostly archived and very old. Because all I'm working on currently is a huge top-secret #shitcode =)
https://git.nicelycomposed.codes/yehor

#development #homelab #selfHosted #selfHosting #selfHost

Moving to Gitea

Well, for the past week I’ve started moving many of my software projects into my own Gitea server at git.digitalcombine.ca. So far I must say the experience has been pretty positive. But I must admit I still do have a lot learn about the server software. The couple of open source projects that I have released, although a bit neglected, have been hosted on github like the majority of projects out there and private projects just hosted through ssh on my own private server. It’s has been a breath of fresh air to have a place to host both public and private projects together with the github like interface.

I do have to admit, it hasn’t been all smooth sailing. When I first started playing the server I began by building it from source. I was pleasantly surprised to find that it had already been packaged for FreeBSD which really simplified everything. This really cemented my decision to use it for my projects. The first stumble I’ve had is attempting to customize it, adding the Digital Combine touch to it. Following the following documentation, so far no luck. This isn’t important at the moment. I’ll dig into this later.

I dug up an older personal project, benford, to start learning the fine details of hosting a repository. While doing this I discovered the ability to sign commits. A feature I’m glad I stumbled on. But trying to configure Gitea to auto sign the merging of pull requests via the web interface hasn’t been working for me. I can do it by the command line though. I guess I’ll have to dive into the logs to try to find out what is happening there. Always love a good rabbit hole 😛

Final little note: Now it seems that the couple little customization’s I’ve made have suddenly taken, very cool :D. One issue down!

🆕 I have written a new post on Zeitfresser: How to Build an Electron Web App with Nativefier and Gitea CI/CD

A comprehensive guide to build your own Linux desktop apps with Nativefier and your Gitea CI/CD Pipeline.

Read the full article here: https://ztfr.eu/how-to-build-an-electron-web-app-with-nativefier-and-gitea-ci-cd/

#app #bash #electron #gitea #Linux #web #wrapper

🆕 I have written a new post on Zeitfresser: How to Build an Electron Web App with Nativefier and Gitea CI/CD

A comprehensive guide to build your own Linux desktop apps with Nativefier and your Gitea CI/CD Pipeline.

Read the full article here: https://ztfr.eu/how-to-build-an-electron-web-app-with-nativefier-and-gitea-ci-cd/

#app #bash #electron #gitea #Linux #web #wrapper

A comprehensive guide to build your own Linux desktop apps with Nativefier and your Gitea CI/CD Pipeline.

A comprehensive guide to build your own Linux desktop apps with Nativefier and your Gitea CI/CD Pipeline.

Is someone using #gitea intensively online in an iPhone in web view? I did and as this was rather inconvenient, I created gyokuro, an iOS gitea and forgejo client.

#git #swift#development

Ich hab mich heute im #urlaubcj mit meinem #garten beschäftigt und in der Zeit, wo's geregnet hat mit #gitea und verteilten #IssueTracker auf basis von #git: https://github.com/remenoscodes/git-native-issue und https://github.com/git-bug/git-bug ) daneben habe ich noch ein wenig mit #plantuml , #tex und #gnuplot rumgespielt und viel über #gitnotes gelernt - etwa hier https://git-scm.com/docs/git-notes und hier https://medium.com/digitalfrontiers/git-your-stuff-together-storing-test-reports-along-your-sources-with-git-notes-f5c8068dc981

Ich hab mich heute im #urlaubcj mit meinem #garten beschäftigt und in der Zeit, wo's geregnet hat mit #gitea und verteilten #IssueTracker auf basis von #git: https://github.com/remenoscodes/git-native-issue und https://github.com/git-bug/git-bug ) daneben habe ich noch ein wenig mit #plantuml , #tex und #gnuplot rumgespielt und viel über #gitnotes gelernt - etwa hier https://git-scm.com/docs/git-notes und hier https://medium.com/digitalfrontiers/git-your-stuff-together-storing-test-reports-along-your-sources-with-git-notes-f5c8068dc981

Ich hab mich heute im #urlaubcj mit meinem #garten beschäftigt und in der Zeit, wo's geregnet hat mit #gitea und verteilten #IssueTracker auf basis von #git: https://github.com/remenoscodes/git-native-issue und https://github.com/git-bug/git-bug ) daneben habe ich noch ein wenig mit #plantuml , #tex und #gnuplot rumgespielt und viel über #gitnotes gelernt - etwa hier https://git-scm.com/docs/git-notes und hier https://medium.com/digitalfrontiers/git-your-stuff-together-storing-test-reports-along-your-sources-with-git-notes-f5c8068dc981

Ich hab mich heute im #urlaubcj mit meinem #garten beschäftigt und in der Zeit, wo's geregnet hat mit #gitea und verteilten #IssueTracker auf basis von #git: https://github.com/remenoscodes/git-native-issue und https://github.com/git-bug/git-bug ) daneben habe ich noch ein wenig mit #plantuml , #tex und #gnuplot rumgespielt und viel über #gitnotes gelernt - etwa hier https://git-scm.com/docs/git-notes und hier https://medium.com/digitalfrontiers/git-your-stuff-together-storing-test-reports-along-your-sources-with-git-notes-f5c8068dc981

It's a proud and huge moment for me to announce GitNex 13.0.0, the most heavily refactored version UI wise. 🎉 🎉 🎉

This release features a completely new UI for GitNex, with everything right at your fingertips. It is a whole new experience this time. Install the app to discover the new features and UI.

The list of features and improvements is long, so it is advised to check the release notes.

Notes: https://codeberg.org/gitnex/GitNex/releases

#gitnex #git #android #codeberg #gitea #forgejo #foss #opensource

It's a proud and huge moment for me to announce GitNex 13.0.0, the most heavily refactored version UI wise. 🎉 🎉 🎉

This release features a completely new UI for GitNex, with everything right at your fingertips. It is a whole new experience this time. Install the app to discover the new features and UI.

The list of features and improvements is long, so it is advised to check the release notes.

Notes: https://codeberg.org/gitnex/GitNex/releases

#gitnex #git #android #codeberg #gitea #forgejo #foss #opensource

It's a proud and huge moment for me to announce GitNex 13.0.0, the most heavily refactored version UI wise. 🎉 🎉 🎉

This release features a completely new UI for GitNex, with everything right at your fingertips. It is a whole new experience this time. Install the app to discover the new features and UI.

The list of features and improvements is long, so it is advised to check the release notes.

Notes: https://codeberg.org/gitnex/GitNex/releases

#gitnex #git #android #codeberg #gitea #forgejo #foss #opensource

It's a proud and huge moment for me to announce GitNex 13.0.0, the most heavily refactored version UI wise. 🎉 🎉 🎉

This release features a completely new UI for GitNex, with everything right at your fingertips. It is a whole new experience this time. Install the app to discover the new features and UI.

The list of features and improvements is long, so it is advised to check the release notes.

Notes: https://codeberg.org/gitnex/GitNex/releases

#gitnex #git #android #codeberg #gitea #forgejo #foss #opensource

It's a proud and huge moment for me to announce GitNex 13.0.0, the most heavily refactored version UI wise. 🎉 🎉 🎉

This release features a completely new UI for GitNex, with everything right at your fingertips. It is a whole new experience this time. Install the app to discover the new features and UI.

The list of features and improvements is long, so it is advised to check the release notes.

Notes: https://codeberg.org/gitnex/GitNex/releases

#gitnex #git #android #codeberg #gitea #forgejo #foss #opensource

I hope everyone had a wonderful Father's Day, despite the bad weather here in Germany. I spent most of the day with my family, but I also managed to write a short article about switching from GitHub to a self-hosted Gitea environment. Happy to share it with you.

https://ztfr.eu/how-to-switch-from-github-to-gitea/

#selfhosting #docker #gitea #github #how-to

I hope everyone had a wonderful Father's Day, despite the bad weather here in Germany. I spent most of the day with my family, but I also managed to write a short article about switching from GitHub to a self-hosted Gitea environment. Happy to share it with you.

https://ztfr.eu/how-to-switch-from-github-to-gitea/

#selfhosting #docker #gitea #github #how-to

I hope everyone had a wonderful Father's Day, despite the bad weather here in Germany. I spent most of the day with my family, but I also managed to write a short article about switching from GitHub to a self-hosted Gitea environment. Happy to share it with you.

https://ztfr.eu/how-to-switch-from-github-to-gitea/

#selfhosting #docker #gitea #github #how-to

I hope everyone had a wonderful Father's Day, despite the bad weather here in Germany. I spent most of the day with my family, but I also managed to write a short article about switching from GitHub to a self-hosted Gitea environment. Happy to share it with you.

https://ztfr.eu/how-to-switch-from-github-to-gitea/

#selfhosting #docker #gitea #github #how-to

https://blog.gslin.org/archives/2026/05/14/13038/forgejo-%e5%9c%a8-2024-%e5%b9%b4%e7%9a%84%e6%8e%88%e6%ac%8a%e6%9b%b4%e6%8f%9b-mit-%e8%bd%89-gplv3/

Forgejo 在 2024 年的授權更換 (MIT 轉 GPLv3+)

#agpl #forgejo #gitea #gpl #license #mit

https://blog.gslin.org/archives/2026/05/14/13038/forgejo-%e5%9c%a8-2024-%e5%b9%b4%e7%9a%84%e6%8e%88%e6%ac%8a%e6%9b%b4%e6%8f%9b-mit-%e8%bd%89-gplv3/

Forgejo 在 2024 年的授權更換 (MIT 轉 GPLv3+)

#agpl #forgejo #gitea #gpl #license #mit

https://blog.gslin.org/archives/2026/05/14/13038/forgejo-%e5%9c%a8-2024-%e5%b9%b4%e7%9a%84%e6%8e%88%e6%ac%8a%e6%9b%b4%e6%8f%9b-mit-%e8%bd%89-gplv3/

Forgejo 在 2024 年的授權更換 (MIT 轉 GPLv3+)

#agpl #forgejo #gitea #gpl #license #mit

https://blog.gslin.org/archives/2026/05/14/13038/forgejo-%e5%9c%a8-2024-%e5%b9%b4%e7%9a%84%e6%8e%88%e6%ac%8a%e6%9b%b4%e6%8f%9b-mit-%e8%bd%89-gplv3/

Forgejo 在 2024 年的授權更換 (MIT 轉 GPLv3+)

#agpl #forgejo #gitea #gpl #license #mit

https://blog.gslin.org/archives/2026/05/14/13038/forgejo-%e5%9c%a8-2024-%e5%b9%b4%e7%9a%84%e6%8e%88%e6%ac%8a%e6%9b%b4%e6%8f%9b-mit-%e8%bd%89-gplv3/

Forgejo 在 2024 年的授權更換 (MIT 轉 GPLv3+)

#agpl #forgejo #gitea #gpl #license #mit

So I'm torn: Forgejo feels better governance-wise, but Gitea feels more practical for my needs today.

#forgejo #gitea

So I'm torn: Forgejo feels better governance-wise, but Gitea feels more practical for my needs today.

#forgejo #gitea

Follow-up on #Forgejo vs #Gitea:

I read more about the split, and I'm still not sure.

I understand the governance concerns around Gitea, and Forgejo’s FOSS/community direction is very appealing.

But #Gitea supports #OpenTofu state, which I need, and I don't think "open source + paid hosting/support" is a bad model. Actually, it can be one of the healthier ways to fund development.

Maintainers should be paid. Good open-source tools need time, money, and boring long-term maintenance.

Follow-up on #Forgejo vs #Gitea:

I read more about the split, and I'm still not sure.

I understand the governance concerns around Gitea, and Forgejo’s FOSS/community direction is very appealing.

But #Gitea supports #OpenTofu state, which I need, and I don't think "open source + paid hosting/support" is a bad model. Actually, it can be one of the healthier ways to fund development.

Maintainers should be paid. Good open-source tools need time, money, and boring long-term maintenance.

Automation is such a beautiful thing, when done safely.

#vpp #gitea #selfhosting

Automation is such a beautiful thing, when done safely.

#vpp #gitea #selfhosting

Automation is such a beautiful thing, when done safely.

#vpp #gitea #selfhosting

Automation is such a beautiful thing, when done safely.

#vpp #gitea #selfhosting

Automation is such a beautiful thing, when done safely.

#vpp #gitea #selfhosting

Ok. Nach der Entwicklung bei #gitlab sehe ich mich nach Alternativen um. #onedev fällt aus: "Built-in AI for DevOps Intelligence" und "Workspaces for Vibe Coding" - würg! #gogs genauso: ich klicke auf der Startseite auf "features" und lande mitten in der Doku unter "authentication" - brauch ich nicht! #radicle hatte ich mir schon mal angesehen und fand's damals zu kompliziert und sinnlos - neues Protokoll, das alles tut, was #git tut - es nur anders nennt - nee... #gitea - hmm, weiß ich nicht..

Ok. Nach der Entwicklung bei #gitlab sehe ich mich nach Alternativen um. #onedev fällt aus: "Built-in AI for DevOps Intelligence" und "Workspaces for Vibe Coding" - würg! #gogs genauso: ich klicke auf der Startseite auf "features" und lande mitten in der Doku unter "authentication" - brauch ich nicht! #radicle hatte ich mir schon mal angesehen und fand's damals zu kompliziert und sinnlos - neues Protokoll, das alles tut, was #git tut - es nur anders nennt - nee... #gitea - hmm, weiß ich nicht..

Ok. Nach der Entwicklung bei #gitlab sehe ich mich nach Alternativen um. #onedev fällt aus: "Built-in AI for DevOps Intelligence" und "Workspaces for Vibe Coding" - würg! #gogs genauso: ich klicke auf der Startseite auf "features" und lande mitten in der Doku unter "authentication" - brauch ich nicht! #radicle hatte ich mir schon mal angesehen und fand's damals zu kompliziert und sinnlos - neues Protokoll, das alles tut, was #git tut - es nur anders nennt - nee... #gitea - hmm, weiß ich nicht..

Ok. Nach der Entwicklung bei #gitlab sehe ich mich nach Alternativen um. #onedev fällt aus: "Built-in AI for DevOps Intelligence" und "Workspaces for Vibe Coding" - würg! #gogs genauso: ich klicke auf der Startseite auf "features" und lande mitten in der Doku unter "authentication" - brauch ich nicht! #radicle hatte ich mir schon mal angesehen und fand's damals zu kompliziert und sinnlos - neues Protokoll, das alles tut, was #git tut - es nur anders nennt - nee... #gitea - hmm, weiß ich nicht..

Ok. Nach der Entwicklung bei #gitlab sehe ich mich nach Alternativen um. #onedev fällt aus: "Built-in AI for DevOps Intelligence" und "Workspaces for Vibe Coding" - würg! #gogs genauso: ich klicke auf der Startseite auf "features" und lande mitten in der Doku unter "authentication" - brauch ich nicht! #radicle hatte ich mir schon mal angesehen und fand's damals zu kompliziert und sinnlos - neues Protokoll, das alles tut, was #git tut - es nur anders nennt - nee... #gitea - hmm, weiß ich nicht..

Self-hosted Git in 2026: Forgejo, Gitea or SourceHut?

I value open-source governance, but I also care about polish, UX, Actions, OpenTofu state, security, and long-term maintenance.

Which would you choose for a small/private team, and why?

#git #forgejo #gitea #sourcehut

Self-hosted Git in 2026: Forgejo, Gitea or SourceHut?

I value open-source governance, but I also care about polish, UX, Actions, OpenTofu state, security, and long-term maintenance.

Which would you choose for a small/private team, and why?

#git #forgejo #gitea #sourcehut