I’ve recently set up my own Gitea instance and I figured I’d share a simple guide on how to do it yourself. Hopefully this will be helpful to anyone looking to get started.

If you have any feedback please feel free to comment it bellow.

  • 4rkal@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    22
    arrow-down
    4
    ·
    23 days ago

    Silly question but what is the problem with gitea being for profit?

    • 9point6@lemmy.world
      link
      fedilink
      English
      arrow-up
      65
      ·
      23 days ago

      I guess out of fear that we get another gitlab situation, where the open source offering has a load of key features eventually kept behind a paywall

    • slazer2au@lemmy.world
      link
      fedilink
      English
      arrow-up
      39
      arrow-down
      2
      ·
      23 days ago

      At some point they will do a Redis or Terraform and say no more open source, pay us to use it.

      All contributions are now owned by us and not by the person who wrote it.

    • Neshura@bookwormstory.social
      link
      fedilink
      English
      arrow-up
      19
      ·
      23 days ago

      As the other commenter already said it’s an abundance of caution. GItea is already moving in the direction of SaaS and an easily self-hostable solution runs counter to that plan (Gitea is already offering a managed Cloud so this is not a hypothetical). One thing that has already happened is Gitea introducing a Contributor License Agreement, effectively allowing them to change the license of the code at any time.