@fstateaudio Yeah I went through the same thing over the past few years.
At this point I find myself valuing cooperative projects more (which incidentally tend to be FOSS, because that infrastructure already exists). Does that make sense?
When I was using and preaching FOSS, I felt like my POV was very individualistic at its core.
Whereas now I've pretty much moved entirely to #Mirlo , #Codeberg , and other similar coop projects.
#qemu is broken with latest #Alpine 3.23
https://gitlab.alpinelinux.org/alpine/aports/-/issues/17775
executing post-install
execve: No such file or directory
#arm #arm64 #crosscompiling #emulation #linuxEmulation #linux #github #gitlab #forgejo #codeberg #cicd #pipeline #pipelines #docker #containers #container #buildx #buildkit #docker_buildx #k8s #kubernetes #golang #controller #operator
I need Codeberg projects to work as nicely as Github projects.
That means getting two features:
1. being able to create an issue directly inside a column. The new issue thing takes me out of the project page.
2. Android app access. I can quickly see what I'm up to on any project on Github android app by going to the project Kanban thing. GitNex is wonderful and seems to be the closest thing to the Github android app, but there's no project viewing feature.
If I get those two, I can literally get out of Github before 2026
I'm migrating to #Codeberg from #Github. I'll probably do it lazily, as I make updates to repos, but it's the right thing to do. https://codeberg.org/biesnecker
Did the TODO. Now old backups are cleaned up.
https://codeberg.org/brybry/gotosocial-sqlite-backup-to-s3/commit/f3ef0a07bebe8822f5b8284fc0a280aefc79a23d61177e321c6759ef6e6cfd6a
#SQLite #gotosocial #Codeberg
Commit 10:
/moved to #codeberg
Gebt das mal als Suche bei #github ein! Heute am 10.12.2025 sind es schon über 1200 Repos. Wieviel kommen bis zum #39c3 wohl noch dazu?
Hier der github Link zur Suche:
\__
#jek25 #cccRegio #OpenSource #wartenauf39c3 #adventskalender #forgejo
Setup daily backups of my #SQLite for my #gotosocial server. Backups go to S3 at the moment but I’ll add just archiving to a local path or maybe scp to a host? I dunno. Don’t need to make things too complicated.
I put the script on #Codeberg for others to use if they want.
TODO: add cleaning up old backups.
https://codeberg.org/brybry/gotosocial-sqlite-backup-to-s3
I'm now on #Codeberg too as user SenseException, in case you want to connect (or burden me with maintaining code 😁).
@tobi schau mal hier: https://blog.codeberg.org/letter-from-codeberg-onwards-and-upwards.html
"git-pages is an alternative to Codeberg Pages, it uses a different approach to serving static pages that is more efficient. Codeberg is planning to gradually migrate to it."
(Soweit ich weiß benutzt #Codeberg den 'mehr foss' fork #forgejo )
@regineheidorn @MeierSchulze @barning
super, gut zu wissen. Ich versuche aktuell eigentlich auch nur #codeberg zu nutzen.
When a person loses access to their TOTP (e.g. phone wiped) and didn't properly save their TOTP's scratch code they have to; they have to rely on the instance admins to authenticate with them that it is really their account, this can be a quite difficult and lengthy process to safely verify this.
Something that has come up in these situations is that such people usually have a (verified) SSH key added to their account and could use that to prove they are the owner of the account, by the possession of such SSH key.
This patch adds a new SSH command that streamlines this process to a self-service, no involvement of instance admins are needed. This is similar to how Gitlab does this: https://gitlab.com/gitlab-org/gitlab-shell/-/merge_requests/74
When the user wants to make use of this self-service, they simply have to execute ssh git@git.example.org totp_recovery_code, they might need to specify with -i ~/.ssh/path_to_key a verified key if this isn't the default key, and confirm they want to regenerate the TOTP recovery code and fill in their password
Commit 09: Nach dem #CLI ist vor der #API. Auch für #codeberg gilt die #forgejo API. Hab noch nie so schnell das #Swagger File gefunden:
Wunderbar geeignet um sich beim #wartenauf39c3 sinnvoll die Zeit zu vertreiben.
\__
#jek25 #OpenAPI #cccRegio #OpenSource #FLOSS #FOSS #39c3 #adventskalender
Im Zuge der Migration meiner #OpenSource-Projekte zu #Codeberg habe ich heute ein #WoodpeckerCI-Plugin gebaut, welches Releases erstellen und (basierend auf einem Pattern) Build-Artefakte anhängen kann. Ich war überrascht, wie einfach das ist! Ein gutes System.
Hier ist ein kurzer Artikel (kein Video!) mit ein bisschen mehr Informationen dazu: https://zephyrsoft.org/create-a-plugin-for-woodpecker-ci/
Because I was also trying out #Codeberg pages, you can check out this demo version: https://kudusch.codeberg.page/terminal_wrapped/
"Sur GitHub, la promotion de l’IA fait fuir certains utilisateurs", alternative européenne : CodeBerg !
#GitHub #IA #Microsoft #Alternatives #CodeBerg ...
https://next.ink/213438/sur-github-la-promotion-de-lia-fait-fuir-certains-utilisateurs/
Update about the future of musi lili. Beside my work on akesi lili I also prepare the next release of my rust retro game engine musi lili. The next releases will not be available on crates.io, because I now longer have an GitHub account, now I have only an account @Codeberg. Unfortunately you need a GitHub account to publish on crates.io. But I don't want a GitHub account to use it only for one use case.
I'll keep you updated.
