codefloe.bsky.social

codefloe.bsky.social

@codefloe.bsky.social

Official codefloe.com account

17 followers5 following20 posts

codefloe.bsky.social
@codefloe.bsky.social

We have added a high-level architecture diagram to our docs. There will of course be continuous changes to this and hence this is only a snapshot of today's state, still we thought it might be worthwhile to share it here! #forgejo #codefloe

codefloe.bsky.social
@codefloe.bsky.social

Following the move to our new, more powerful server a few days ago, we have now also enabled code search (via the new zoekt option available in Forgejo v16). Code search is restricted to logged-in users to prevent anonymous abuse. #codefloe #forgejo

codefloe.bsky.social
@codefloe.bsky.social

Now that #codeberg has manifested their anti-AI view with a 70% in favor vote (codeberg.org/Codeberg/org...), we're happy to welcome (once again) all the people which have to/want to move their repositories off CB but still want to stay on a Forgejo-based instance. #codefloe #giveUpGitHub

codeberg.orgProposal Assembly 2026: ToU extension to prohibit LLM-extrusionsHere is the proposed addition for the ToU that @Gusted and I agreed on post-assembly for the upcoming membership vote. 🙏 The discussion for this proposal is available for Codeberg e. V. members in th...
codefloe.bsky.social
@codefloe.bsky.social

Bonus: on top you'll get better uptime, faster site responses and faster CI runners - all for free :) tl;dr: after this ToU change, keeping AI-generated code on Codeberg would violate these and repositories will be in danger of deletion.

codefloe.bsky.social
@codefloe.bsky.social

We've add an account quick-switch option that allows you to change between multiple accounts without going through the full login/logout flow every time. Try it out and tell us if something doesn't work or you'd like to have something changed! #forgejo #codefloe

codefloe.bsky.social
@codefloe.bsky.social

We've created a infrastructure cost report including donations from the creation of our platform until today. Read more at forum.codefloe.com/t/2026-05-01... #codefloe #giveUpGitHub #forgejo

forum.codefloe.com2026-05-01: Platform cost analyticsIn addition to our quarterly platform analytics, which focus on user and repository metrics, we have now also explored the financial side to produce a report. The aim is to give users an overview of what it costs to run the platform, how the money is spent, and how much funding is coming in through donations via Liberapay (thanks to every sponsor!). Cost Summary Report Index of monthly cost reports A few notes about this graph: Our current resources on PROD are way larger than what we c...
codefloe.bsky.social
@codefloe.bsky.social

Our hosted #renovate bot now runs via the mogenius/renovate-operator. This enables webhook-based support, i.e. clicking the checkboxes in the renovate dashboard and PR actions now have an effect! Read more here: forum.codefloe.com/t/2026-03-30... #codefloe #forgejo #renovate #giveUpGitHub

forum.codefloe.com2026-03-30: Improvements to the hosted Renovate botOver the course of the last weeks we refactored how the Renovate bot performs it’s actions on repositories. Historically, the bot ran once per hour on all repos it has access to in sequential order. This caused the job to take around 35 minutes already for around 100 repos it had to process. The runtime includes both enabled dependency and repo caches. Given that CodeFloe has it’s own k8s cluster since some time, we stumbled over https://github.com/mogenius/renovate-operator. This k8s operator...
codefloe.bsky.social
@codefloe.bsky.social

We just concluded today's maintenance: - Forgejo: v13 -> v14 - Postgres: v17 -> v18 Crow CI, Meilisearch, Valkey and other related services have also been upgraded. #codefloe #forgejo #codeberg #git

codefloe.bsky.social
@codefloe.bsky.social

Various Forgejo Actions improvements; Update to Crow v4.4.0; IPV6 support More details at forum.codefloe.com/t/2025-11-03... #codefloe #forgejo #GiveUpGitHub

forum.codefloe.com2025-11-03: Various Forgejo Actions improvements; Update to Crow v4.4.0; IPV6 supportForgejo Actions configuration has seen lots of improvements over the last days. Docker workflows are now supported through a dedicated docker-in-docker (DIND) instance processing all workflows. See...

You are up to date.