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.

  • Neshura
    link
    fedilink
    English
    153
    edit-2
    4 months ago

    I’ll be that guy: Use forgejo instead, its main contributor is a Non-Profit compared to Gitea’s For-Profit owners

      • @[email protected]
        link
        fedilink
        English
        644 months 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
        link
        fedilink
        English
        394 months 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
        link
        fedilink
        English
        194 months 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.

    • @PenisDuckCuck9001
      link
      English
      9
      edit-2
      4 months ago

      Thanks, I always keep forgetting what this ones called. I use a build of gitea from before it became shit but I keep telling myself I need to change to “that better one”.