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.

  • @[email protected]OP
    link
    fedilink
    English
    24 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.

    • @[email protected]
      link
      fedilink
      English
      44 months ago

      If you have a place to host Forgejo/Gitea, you have a place to store a Git server. Set it up like this:

      $ git clone --bare myrepo myrepo.bare
      $ scp -r myrepo.bare srv:
      $ cd myrepo
      $ git remote add origin srv:myrepo.bare
      # or
      $ git remote set-url origin srv:myrepo.bare
      

      Now git push etc work similar to GitHub, but you’re using your server (named srv in SSH config, as shown in my previous post) as the remote storage.

      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.

      • @[email protected]
        link
        fedilink
        English
        5
        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.