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@bookwormstory.social
    link
    fedilink
    English
    arrow-up
    152
    arrow-down
    6
    ·
    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

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

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

      • 9point6@lemmy.world
        link
        fedilink
        English
        arrow-up
        65
        ·
        4 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@lemmy.world
        link
        fedilink
        English
        arrow-up
        39
        arrow-down
        2
        ·
        4 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@bookwormstory.social
        link
        fedilink
        English
        arrow-up
        19
        ·
        4 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@lemmynsfw.com
      link
      fedilink
      English
      arrow-up
      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”.

    • 4rkal@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 months ago

      Great question

      I always found setting up a git server from scratch to be quite confusing and I also like the webui that gitea offers.

      But recently I have also started moving some of my github projects there so having a link (with a readme and everything) that I can share with others is important.

        • asap@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          edit-2
          4 months ago

          Selfhosted Gitea is a way to get a wiki, bug tracker or whatnot - collaborate, for example, but it’s not necessary to have a Git server for your personal use.

          No, but it is amazing for browsing your repos and visually seeing what you did in a past commit or a branch, while your IDE is open to your latest code. Or copying and pasting something that you need from a different repo.

          For Git experts, sure they can probably do all that better inside their IDE or CLI, but for us plebs, having your own Forgejo is incredible 😍

          I have mine configured to disable the wiki and issues, etc, it’s just the repo browser.

    • Miaou@jlai.lu
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 months ago

      I’m hoping federation will allow me to get rid of my github entirely, but that’s wishful thinking I fear

  • Toribor@corndog.social
    link
    fedilink
    English
    arrow-up
    6
    ·
    4 months ago

    I intentionally do not host my own git repos mostly because I need them to be available when my environment is having problems.

    I make use of local runners for CI/CD though which is nice but git is one of the few things I need to not have to worry about.

  • ramenu@lemmy.ml
    link
    fedilink
    English
    arrow-up
    5
    ·
    4 months ago

    Sidenote: If you just want a nice web frontend for others to view your Git repositories, you can use cgit instead.

      • JackbyDev@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 months ago

        After dealing with tcl errors trying to test sqlite, I feel I’ve never seen a more scathing criticism of fossil.

      • JackbyDev@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 months ago

        I love love love that Fossil is a single executable.

        All in all, the version control wars have ended and git has won. Mercurial is another one I sort of wanna try just to see what it’s like.

        Re: rebasing, I think squashing / rebasing (in place of merging) is bad but I am also one of the few people I know who tries to make a good history with good commit messages prior to opening a pull request by using interactive rebasing. (This topic is confusing to talk about because I have to say “I don’t rebase, instead o rebase” which can be confusing.)