CodeFloe

@lehtimaeki please open a thread in the forum for such requests, Mastodon isn't the perfect place for such topics :)

We would need to know how the request shape looks like, I.e. User agent, request frequency, etc to be able to help.

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

@adamhsparks thanks for your feedback!

We already do so when announcing maintenance downtime. So yes, we could make use of this logic for such important messages as well then.

@adamhsparks See our recent posts or the forum announcement :) all good.

Let us know how we can best transport such important messages to users without having to write an email to all :) (maybe we should do so for such critical changes anyhow)

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

@cichy1173 you can set up a push mirror in the repo settings. This way each push to your repo will also appear on GH without additional action.

@cichy1173 you're the first one to appreciate and callout our CI runner speed - appreciated :)

We've recently added some new CI servers and have updated the respective docs page with details about the underlying hardware a few days ago: https://docs.codefloe.com/cicd/hardware/

A global announcement for this is still pending.

#codefloe #cicd

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

@philvessey welcome ✌️enjoy and have fun.

New feature: Pull Request preview environments!

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

#codefloe #forgejo

@strk It's likely safe to assume that, unless there's a policy, no restriction applies. Codeberg is not the default but the exception.

So yes, AI content is allowed.

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

@cichy1173 https://codefloe.com/codefloe/forgejo-batch-migrate is ready for testing - please report issues in the repo directly :)

@cichy1173 Thanks for the feedback! Please give us some hours until we've packaged the first release.

If you have feedback, feel free to open an issue in the repo 🙂️

@cichy1173 Good idea! About time to create a dedicated tool for this - we're on it: https://codefloe.com/codefloe/forgejo-batch-migrate

@gedankenstuecke @jaredwhite @pat_dev

We offer custom contracts and extra limits to users who ask for it. This way we combine the best out of two worlds: a donation-based model for individuals and others that value a fast and open but privacy aware platform while they decide on their own how much they want to give. This money is directly invested into the infrastructure stack.

In contrast to #codeberg, contributions are not bound to a single currency and the minimum of 5/m. It also doesn't come with an required association membership. They can just support the product/platform they are making use of.