Being "professionally hosted" is not enough: You need a "cluefully developed" distributed git backend to be a GitHub competitor. Codeberg is already buckling despite being nowhere near GitHub's scale. When Codefloe gains more users/agents, it's going to suffer from the same fate since Forgejo/Gitea/Gogs just isn't a good foundation to build on top of.
I've ported a couple of repos to CodeFloe in the last few days, and so far, so good. Performance is similar to when I self-host Forgejo on a dedicated VPS where I'm the only user, which is super fast. And their built-in CI is pretty nice.
It's a huge contrast to Codeberg, which struggles with basic navigation of the web UI and every git push or pull takes 2-10s.
> Performance is similar to when I self-host Forgejo on a dedicated VPS where I'm the only user, which is super fast.
I don't mean to be negative, but that's probably because it's pretty much the same thing. Codefloe is tiny. Some quick counting shows it has a grand total of 1012 registered users, including bots, and 1416 public repositories of which the top 3 with the most stars (I know this is a mostly meaningless metric, but for scale) have 27, 13, and 8. It's too small to run into scaling issues.
That’s an interesting question - it’s one thing to run an instance of forgejo for a limited user base and another to run at mass public scale.
How does someplace like a GitHub/Gitlab go it? Are user accounts or repos sharded across different servers? Is there a different underlying scaling system? If one wanted to run Forgejo “at scale” what would it really require, or does this need to be factored into the design from day one?
"In no event shall CodeFloe or its suppliers be liable for any damages (including, without limitation, damages for loss of data or profit, or due to business interruption)"
So many fly-by-night "github replacements" popping up. Step 1, buy a hetzner dedi server from the auction for $100/mo. Step 2, install Forgejo. Step 3, ride the wave of anti-US, anti-big-corp senitment to get users onto your platform. Step 4, an HDD fails in your i9-13900k and you lose half of your users' data.
If you are going to offer hosting, you need to state what kind of guarantees around data protection you offer.
I think you're holding CodeFloe to an unreasonably high standard here. What SaaS vendors agree to financial guarantees if they lose user data or have an outage?
Here's GitHub's policy:
> We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement.
> 14.1. Damages Waiver. Except for Excluded Claims or Special Claims, to the maximum extent permitted by Law, neither party will have any liability arising out of or related to this Agreement for any loss of use, lost data, lost profits, interruption of business or any indirect, special, incidental, reliance or consequential damages of any kind, even if informed of their possibility in advance.
Now, they're not written in terms of compensatory or consequential damages, but you will be entitled to a service credit (which is a "financial guarantee" of sorts) if the conditions are met.
Private agreements frequently have these sorts of provisions as well. You need to be a pretty big or strategic customer to get those, though, and they're often paired hand-in-hand with long-term agreements with mandatory minimum spend.
That is fair. This was just the only thing in their terms that I could find that made any mention in regards to data protection. If you are running a service like this, some kind of SLA should exist. I am less concerned with financial protections and more concerned with data protection.
At the very least, the main guy behind this is pat-s who was originally a WoodpeckerCI dev and has been in and around Codeberg/Forgejo/Woodpecker for a while so I trust he knows his stuff. His work on CrowCI (Woodpecker fork) has been great.
I also swear I've read that same "buy a hetzener dedi install forgejo" etc etc line before, but maybe it's just you're not the only person cynical about the situation.
> Short version: We provide our service as is, and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.
> Short version: We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.
Being "professionally hosted" is not enough: You need a "cluefully developed" distributed git backend to be a GitHub competitor. Codeberg is already buckling despite being nowhere near GitHub's scale. When Codefloe gains more users/agents, it's going to suffer from the same fate since Forgejo/Gitea/Gogs just isn't a good foundation to build on top of.
What do you think makes it a bad foundation to build on?
I've ported a couple of repos to CodeFloe in the last few days, and so far, so good. Performance is similar to when I self-host Forgejo on a dedicated VPS where I'm the only user, which is super fast. And their built-in CI is pretty nice.
It's a huge contrast to Codeberg, which struggles with basic navigation of the web UI and every git push or pull takes 2-10s.
> Performance is similar to when I self-host Forgejo on a dedicated VPS where I'm the only user, which is super fast.
I don't mean to be negative, but that's probably because it's pretty much the same thing. Codefloe is tiny. Some quick counting shows it has a grand total of 1012 registered users, including bots, and 1416 public repositories of which the top 3 with the most stars (I know this is a mostly meaningless metric, but for scale) have 27, 13, and 8. It's too small to run into scaling issues.
That’s an interesting question - it’s one thing to run an instance of forgejo for a limited user base and another to run at mass public scale.
How does someplace like a GitHub/Gitlab go it? Are user accounts or repos sharded across different servers? Is there a different underlying scaling system? If one wanted to run Forgejo “at scale” what would it really require, or does this need to be factored into the design from day one?
This recent post that made it to the front page talks a lot about approaches GitHub has taken over its history:
https://cursor.com/blog/git-at-any-scale
What makes this different than Codeberg?
Allowing heavily AI projects, from a glance.
Codeberg is for open source projects only. This is for anyone.
"In no event shall CodeFloe or its suppliers be liable for any damages (including, without limitation, damages for loss of data or profit, or due to business interruption)"
So many fly-by-night "github replacements" popping up. Step 1, buy a hetzner dedi server from the auction for $100/mo. Step 2, install Forgejo. Step 3, ride the wave of anti-US, anti-big-corp senitment to get users onto your platform. Step 4, an HDD fails in your i9-13900k and you lose half of your users' data.
If you are going to offer hosting, you need to state what kind of guarantees around data protection you offer.
I think you're holding CodeFloe to an unreasonably high standard here. What SaaS vendors agree to financial guarantees if they lose user data or have an outage?
Here's GitHub's policy:
> We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement.
https://docs.github.com/en/site-policy/github-terms/github-t...
Here's Atlassian's policy for BitBucket:
> 14. Limitations of Liability
> 14.1. Damages Waiver. Except for Excluded Claims or Special Claims, to the maximum extent permitted by Law, neither party will have any liability arising out of or related to this Agreement for any loss of use, lost data, lost profits, interruption of business or any indirect, special, incidental, reliance or consequential damages of any kind, even if informed of their possibility in advance.
https://www.atlassian.com/legal/atlassian-customer-agreement...
> What SaaS vendors agree to financial guarantees if they lose user data or have an outage?
Lots of them. See, e.g., https://aws.amazon.com/compute/sla/
Now, they're not written in terms of compensatory or consequential damages, but you will be entitled to a service credit (which is a "financial guarantee" of sorts) if the conditions are met.
Private agreements frequently have these sorts of provisions as well. You need to be a pretty big or strategic customer to get those, though, and they're often paired hand-in-hand with long-term agreements with mandatory minimum spend.
That is fair. This was just the only thing in their terms that I could find that made any mention in regards to data protection. If you are running a service like this, some kind of SLA should exist. I am less concerned with financial protections and more concerned with data protection.
At the very least, the main guy behind this is pat-s who was originally a WoodpeckerCI dev and has been in and around Codeberg/Forgejo/Woodpecker for a while so I trust he knows his stuff. His work on CrowCI (Woodpecker fork) has been great.
I also swear I've read that same "buy a hetzener dedi install forgejo" etc etc line before, but maybe it's just you're not the only person cynical about the situation.
What kind of guarantres does Github offer?
> Short version: We provide our service as is, and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.
https://docs.github.com/en/site-policy/github-terms/github-t...
> Short version: We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.
https://docs.github.com/en/site-policy/github-terms/github-t...
None. But I'm willing to bet they'll still be around in 3 years.