• drudoo@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 year ago

    Is the consensus to migrate to Forgejo or stay with Gitea? I’m running Gitea using docked and wondering how to migrate my setup to Forgejo, if needed.

    • estebanlm@lemmy.ml
      link
      fedilink
      English
      arrow-up
      13
      ·
      1 year ago

      I do not think there is a consensus. Personally, I am not moving anytime soon. IMO so far gitea has not done anything wrong yet (they just put them in a position where is easier for them to do it, eventually). It is still a good thing forgejo exists… but I can’t stand the name, heh (also, I like the green theme of gitea :P).

    • CodeGameEat@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 year ago

      Personally I am conflicted. On one side gitea switching to a for-profit is worrying, even if they didnt do anything wrong yet. I like codeberg (non-profit behind Forgejo), but I also want to support devs actually working on the product. So I think for now I’ll stay with gitea, but I won’t hesitate to migrate to Forgejo if they start to act stupid

    • terribleplan@lemmy.nrd.li
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      I switched to Fogejo just by swapping out the image. So far gitea hasn’t been malicious with its trademarks now being owned by a private company, but I feel better using software that is more closely tied to a nonprofit. I see no reason to switch back.

    • mariom@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Probably switching container from gitea to forgejo will just work… I recently switched my deployment, “issues” I had with postgres, but it was related to updates on helm-chart part (gitea upgraded postgres as well, so either update or switch made me same work to do).