A shoutout to the amazing pub.solar community, who run several digital services, including #Nextcloud, #Forgejo, #Matrix and #Mastodon.
The community is very friendly and the server is running just fine
You can also set up your own website under yourname.lunar.page by easily creating a git repository on the forgejo server
Huh, my ssh-tpm-agent project is in the #forgejo docs?
https://forgejo.org/docs/next/admin/advanced/signing/#using-ssh-tpm-agent
Cool.
Do I have any #Forgejo experts among my followers who can tell me if I can #mirror a single branch from one #repository to another? And if: how?
Only one branch, not the whole repo.
And here another one: #gitAnnex is notorious for making many commits in the background to the branches synced/<yourbranch>, synced/git-annex and git-annex. These have a perfectly valid technical reason and make git annex as awesome as it is, but in a #forgejo dashboard feed, these are massively confusing as they mask the really important changes. With a little bit of template massaging, these can be filtered out. Probably better to make this configurable somehow (checkbox? ), but this is a workable solution for now.
It's very useful if you self-host the #FOSS tools you need, because then you can fix little issues you have here and there on your own.
For example, we use #forgejoAneksajo (#forgejo with #gitAnnex support) to sync and collaborate on code and data. We often have long filenames, which are unfortunately obstructed by forgejo's gigantic commit message column But a bit of #CSS later and that's fixed so we can more easily browse through our multicopter flight plots
Good news after unpacking post thunderstorm: The #Codeberg and #Forgejo stickers for the @BOSC #CoFest at #ISMBECCB2025 conference are fine - just some of my clothes that were by the bag zip got damp, but they should dry out for later in the week.
#forgejo updated, i can go to sleep in peace
@forgejo My personal highlight of this release: You can now use your #fediverse handle in #markdown documents and it will be marked up as a link to your user profile (or group, etc.).
https://forgejo.org/2025-07-release-v12-0/#redirecting-fediverse-handles
I'm excited about the future, when mentioning fediverse handles will actually be federated and will send notifications everywhere!
#Forgejo #Federation #forgefed
#Forgejo 12.0.0 was just released!
Learn about it in detail in the blog post:
https://forgejo.org/2025-07-release-v12-0/
We recommend that all installations are upgraded to the latest version.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#emacs #fjEl #forgejo #codeberg
fj.el release 0.16
- bind r to add reaction to item at point
- ensure sane default for sorting of issues/repos where possible
- overhaul rendering of item body HTML (for performance reasons)
- defcustom fj-timeline-default-items (for performance reasons)
- respect verbatim/code formatting in item titles and and timeline messages
- bind > to load more items in item timeline view
- include compose buffers in switch to fj buffer / kill all fj buffers
- fix a bunch of (contextually) broken commands
- i also worked on an api layer, but got sidetracked with jag.el, which attempts to do api client library code generation based on Swagger/OpenAPI (WIP)
Holler if you run into any issues upon updating.
if you appreciate my work on fj.el, consider donating:
https://paypal.me/martianh. (even a small amount is appreciated.)
& thanks a lot to the recent donors!
I've just installed #Forgejo in a #FreeBSD Jail, but I couldn't find a guide on how to set it up.
Luckily, I could get away with using the instructions of @marzlberger 's blog post on installing Gitea: https://bsdbox.de/en/artikel/gitea/gitea-lokal
The steps were basically identical, I just had to replace "gitea" with "forgejo" in all the commands and paths.
If I ever want to migrate my Gitea instance to Forgejo, I now know how to do it.
My next Open Source project will use #forgejo for git, release and issue management according to the Collective Code Construction Contract (C4 )process [1] (so no lengthy discussions in issues, only problems and solutions). A static landing page with documentation. A read-only archive of the mailing list posts. And only e-mail to communicate. No chat, no discord.
The goal is to slow everything down. So that devs can concentrate and users learn to use documentation and archive before asking.
@umphy #gitAnnex and
#dataLad organize the data and sync it to our own
#forgejoAneksajo instance. You can instantly see if everything is there and worked. A great workflow!
Well... Every time I create a repository on my self-hosted Forgejo I set the object format to sha256, because I thought any modern things should work fine.
It so happens that Flux only talks to repos in sha1 format.
#Forgejo 11.0.3 and 7.0.16 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
I just enabled the federation on my Forgejo instance, and I don't see many ways to try it out...
I found a small blog post online about having to "sync" two repos via a common federated URL directly through the settings of each repo
Is there anything else currently supported by Forgejo at the federation level ?
If anyone wants to give it a try, feel free to contact me on Matrix https://matrix.to/#/@docyeet:halis.io or directly on my instance