Crumb
c/forgejo · by ctrl_alt_esc@lemmy.ml · 1y

code.forgejo.org vs codeberg.org

The difference between forgejo and codeberg.org is clear. Forgejo is the software and codeberg is the entity that owns it, provides the domain name, etc. and also hosts a public forgejo instance at codeberg.org.

Lately, I've seen that there is also code.forgejo.org, which I assume is run by the same people. Why are there two public instances run by the same organisation? Are users supposed to migrate from one to the other? I see that code.forgejo.org currently has version 11.0 deployed which afaik is not released yet, so is that instance just for testing purposes?

12 points · 4 comments · view on lemmy.world

4 Comments

starshipwinepineapple@programming.dev · 4 pts · 1y (3 replies)

I see that code.forgejo.org currently has version 11.0 deployed which afaik is not released yet, so is that instance just for testing purposes?

Correct, you just don't see the disclaimer if you go straight to code.forgejo.org. if you are on the main forgejo page and click "try it now" you'll see the disclaimer:

"FOR TESTING ONLY, ALL DATA CAN BE WIPED OUT AT ANY TIME"

So to break it down:

  • codeberg e.V. - nonprofit democratic organization that owns codeberg.org and forgejo (or at least funds forgejo)
  • Codeberg.org a public forge that runs forgejo
  • forgejo.org - the forge software that can be self hosted
  • code.forgejo.org - test public forge, data can be deleted without notice

Also worth noting there are other public instances of forgejo and codeberg also encourages of alternative libre forges

ctrl_alt_esc@lemmy.ml · 2 pts · 1y

Thank you for the clarification! I indeed hadn't seen that disclaimer. I'm aware of the other public instances, I was just wondering why codeberg itself would host multiple.

The reason I started noticing this is because I saw projects like https://code.forgejo.org/renovate/renovate which seems to have migrated to https://codeberg.org/forgejo-contrib/forgejo-renovate, but the images are still only available on code.forgejo.org (or is it data.forgejo.org which is used for the image URLs in the repo?). I suppose if code.forgejo.org is for testing only, one also shouldn't pull images from its registry.

forgejo@floss.social · 2 pts · 1y (1 reply)

@starshipwinepineapple @ctrl_alt_esc Hi, I'd like to clarify a bit the confusion about the various instances of Forgejo:

  1. https://codeberg.org/ — a public instance, run by @Codeberg
  2. https://code.forgejo.org/ — instance used by Forgejo contributors for development, e.g. of the Forgejo Runner
  3. https://data.forgejo.org/ — currently points to 2.
  4. https://*.next.forgejo.org/ — test instances, updated daily for supported and upcoming versions (currently v7, try=v11 and v12)
    ~ @mahlzahn
forgejo@floss.social · 1 pts · 1y

@starshipwinepineapple @ctrl_alt_esc
https://data.forgejo.org/ is the default place to get actions from that can be used within CI workflows. It may in the future be a readonly and restricted inatance (to increase availability and resistance to crawlers, etc.)
~ @mahlzahn