CodeFloe

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

Due to our host migration, our SSH fingerprints have changed.

The new ones are listed at https://docs.codefloe.com/usage/ssh/#host-key-fingerprints

You can update these on your boxes as follows:

ssh-keygen -R codefloe.com
ssh -T git@codefloe.com

#codefloe

Migration finished. All went well!

Site should feel a bit faster now than before due to the underlying host now running on 8C/32G and a single CPU score of ~ 3k (GB6) - the host before had a SC value ~ 1k.

Migration went without issues. We're now waiting for the new SSL certs via DNS challenge.

CF now resolves to multiple IPs instead of just one, so this takes a bit.

We're starting the announced maintenance now in which we will move to a new host machine.

Updates in this thread!

We will migrate Forgejo from a Cloud VM to a Proxmox VM (AX102 base) this Friday. This will result in a short downtime of the instance during migration.

The new server has double single core performance and a much faster (datacenter) NVME, so interacting with the instance should become (even) faster afterwards.

Sneak peek: we are currently also working on enabling code search (via zoekt) and migrating Meilisearch to a HA Typesense cluster.

#codefloe #forgejo

Catodon repo moved to Codefloe

Following Codeberg's recent decisions about projects developed with the use of AI, we have moved to @codefloe@social.tchncs.de . The new Catodon repo url is https://codefloe.com/catodon/catodon - please update your git remote!

We are thankful to Codeberg for hosting us so far, but we will not apologize for utilizing one of the biggest technological breakthroughs in decades for the development of open source software, nor for spending countless hours in order to create a great fediverse platform with unique features, bridging the microblogging and the threadiverse sides of fedi. If you need to judge the project, you can judge it by the end result instead of the tools we use for development.

We prefer not to be judged for just doing what we love and making it available to everyone for free, though, so we're excited to join Codefloe!

#catodon #codefloe #codeberg

New feature: Pull Request preview environments!

Read more at
https://forum.codefloe.com/t/2026-07-27-pr-preview-environments/135

#codefloe #forgejo

To do @Codeberg a favor and increase forge freedom and flexibility, we've created a CLI tool to batch migrate repositories between forges.

This way, all the people who want to (or have to) migrate off from #codeberg can do so in a much faster pace, freeing up more space at Codeberg for valuable non-LLM related projects.

The CLI tool is also advertised in our migration UI view.

https://codefloe.com/codefloe/forgejo-batch-migrate

@badsector

Should be working now! Let us know in case you encounter further problems!

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

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.

#codeberg #codefloe #giveUpGitHub