201
GitHub Has an Availability Problem. Is It Time to Look Elsewhere? (dhruv2038.bearblog.dev)
submitted 1 week ago by to c/selfhosted@lemmy.world
63 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 30 points 1 week ago (1 child)

Self-hosted Forgejo works well for my own use. My employer is moving to GitHub Enterprise where it’s a separate instance per company with certain infra shared. Should be a slight improvement, I guess, though probably not a bad idea to make sure internal tooling is built with the git forge being configurable. 😉

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 12 points 1 week ago (1 child)

    I've been eyeing Gitea. Do you have any reason for using Forgejo that I might overlook Gitea in favor of it?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 22 points 1 week ago (1 child)

    I used to run Gitea and switched to Forgejo mainly because I prefer a community project over one run by a for-profit company. I never had any substantive complaints against Gitea during my time with it to be honest, but thought I’d get off of it before investing too much further in case it went in a bad direction.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 13 points 1 week ago (1 child)

    That is a solid enough reason and one I wasn't aware of. Exactly the kind of thing I was hoping to find out, thank you!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 week ago

    The transition of gitea to chasing profits was pretty messy too iirc and motivated the forgejo fork. Gitea lost a lot of good-will back then. Forgejo is also the base that codeberg runs on now.

  • permalink
  • fedilink
  • source
  • parent