Suche
Beiträge, die mit Forgejo getaggt sind
#Forgejo 10.0.2 was just released!
We recommend that all installations are upgraded to the latest version.
Check out the release notes and download it at forgejo.org/releases/. If you experience any issues with this release, please report to codeberg.org/forgejo/forgejo/i….
#Blind users, users that rely heavily on #keyboardNavigation or anyone else with a preference on that matter (please indicate what applies in the comments):
Do you have a preference for or comments on the format of URLs? During user research, we have learned that URLs that are easy to handle are a good thing.
We are currently considering to introduce URLs that do not need more reserved usernames in #Forgejo, such as codeberg.org/-/something/ or codeberg.org/_something/.
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
FOSDEM impressions were published and feedback is being collected regarding migrations to Forgejo and commercial usages of Forgejo. code.forgejo.org got hit by a DDoS that was successfully mitigated. A new localization component is now in use and work on federation continued.
Hi everyone, GitNex 8.0.0 is now out with numerous new features and UI refinements.
- User activity heatmap on the profile
- Dependencies for issues and prs
- Tracked time for issues and prs
- Search within files
- Filter issues by labels
- Filter issues where I am mentioned
- and more...
It's time to update! 🎉
Release notes: codeberg.org/gitnex/GitNex/rel…
#gitnex #gitea #forgejo #codeberg #android #app #git
GitNex
Android client for Forgejo(https://codeberg.org), Gitea(https://gitea.com) [OR your custom hosted server]Forgejo: Beyond coding. We Forge.
GitNex 8.0.0 will be released soon and I want share the exciting news about its features.
It's feature packed and heavy on UI enhancements.
Check them out here: codeberg.org/gitnex/GitNex/mil…
If you find GitNex useful, you can buy the Play version or become a patreon to support the development. 😀
Stay tuned, release is due soon.
#gitnex #gitea #forgejo #android #app #git #codeberg
GitNex
Android client for Forgejo(https://codeberg.org), Gitea(https://gitea.com) [OR your custom hosted server]Codeberg.org
A lot of people seem to suggest you to move to an instance of Forgejo or even Codeberg. We hope you are not overwhelmed or annoyed by this, and wish you all the best for returning back to work with your project ASAP.
If you indeed consider moving to #Forgejo or #Codeberg in the future, feel free to add your project to codeberg.org/forgejo-contrib/m… and let us know if we can be of any assistance to you.
#ayuda fediverso
que solucion es mejor para hacer #backup de un servidor (los archivos)?
aplicaciones en #docker , como #bludit , #forgejo , #peertube entre otras..
querria algo que tenga #versioning y soporte #s3 e idealmente interfaz web para gestionar.
estoy probando #backrest pero no veo que tenga versioning?
@t3rr0rz0n3 @matiargs @pijusmagnificus @samcre
se agradece #boost
The events of the past weeks have again upped the urgency of moving away from the US tech cloud. After forever Google and 18 years GitHub this is hard for me.
I am lucky that @distribits gave me the enthusiasm and the tools to make this happen for me and the #infrastructure of the #research group I am heading.
This is the first post in a series that documents our new #selfhosted setup, starting with the centerpiece forgejo-aneksajo -- #forgejo with #gitAnnex built in.
blog.datalad.org/posts/lab-inf…
Collaborative infrastructure for a lab: Forgejo
The first installment of a mini-series on a self-hosted, collaborative infrastructure: Run Forgejo on a small VPS or NAS as a central collaboration platform for a lab or group.Michael Hanke (To be distributed...)
Interested in the state of #federation at #Forgejo ?
We gave an fast overview on what's going on at the #fosdem25 . Video is now available:
#Gitea vs. #Forgejo puzzles me a bit. From the outside, this looks much like a people don't like each other problem.
Gitea is still alive & OSS. Forgejo has 2k+ more commits, looks like that's mostly because they update dependencies like crazy.
I've got them both installed and they still look/feel/work exactly the same.
Are you using #github for #FOSS ?
Small request: could you use FOSS instead?
Don't make #Microsoft your gatekeeper, use like #forgejo #codeberg or something.
sfconservancy.org/GiveUpGitHub…
Thanks to @conservancy 's @karen , Denver Gingerich and Bradley Kuhn for the #FOSDEM talk.
Give Up GitHub - Software Freedom Conservancy
The Software Freedom Conservancy provides a non-profit home and services to Free, Libre and Open Source Software (FLOSS) projects.sfconservancy.org
Meet us at #FOSDEM and get stickers for #Codeberg, #Forgejo, #IzzyOnDroid, meet the team, chat about our community, in-flight features, infrastructure and contributions.
UA building, you will see our rollup.
Enough mucking around with these Forgejo runners. I have a working solution, which is not the best, but it's functional, and is what I need to finish the blog post. At some point in the future I can think about version 2.0, with a better container image (or my own, who knows).
Okay, here's something that is killing my Forgejo runner experiment: I need the perfect container image. The ones I have tried so far are missing one thing or another, and it's taking me a while to deal with that.
So, instead of trying to build my own image, let me ask the hive mind if anyone knows of a single *reliable* container image that has all of the following *already* installed: Python, NodeJS and Docker CE (or Podman).
And no, I'm not looking for a container image built buy a random guy for their own personal use. That guy could be me. I really want something that is supported as part of a larger project.
My sanity thanks you.
Ugh! I created a complication for my own self.
While writing a blog post about my findings related to Forgejo runner on a Raspberry Pi, I realized that I also needed a runner to build x86 (amd64) images. So now I am adding a lot more steps to my setup (still debating between LXC or KVM on Proxmox).
The blog post has been severely delayed.
Fun! While writing a blog post about my findings related to Forgejo runner and Docker-in-Docker, I realized I made a few mistakes, and was able to fix them.
So that proves that old saying: the best way to learn, is to teach.
Sometimes we do complex stuff just for the sake of learning, and that's the essence of why we have home labs.
I built a Fedora container image (for an Ansible execution environment), from inside an Ubuntu container, that is running inside another Ubuntu container (Forgejo runner), while all of them were using the same underlying Docker-in-Docker, running from a Docker Compose (where Forgejo and the Runner also are), on a Debian base OS, on a Raspberry Pi.
Did I need to do that? Absolutely not. Did I like doing it? Obviously yes!
Now I just need to find the time and the head space to write a blog post about it. 😄