Selfhost your own gitea instance - selfhosted, lightweight github alternative | 4rkal's blog
4rkal.com
In this article I’ll walk you through how you can run your own gitea instance. But first What is gitea? Gitea is a painless selfhosted Git service. It is written in Go and is extremely lightweight. I run a gitea instance on my Le Potato and it barely uses any resources. Why use gitea (vs GitHub, GitLab etc) I started running my own Gitea instance because I wanted a private place to host my Obsidian notes.

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.

      • JackbyDev@programming.devEnglish
        2·
        3 months ago

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

    • cizra@lemm.eeEnglish
      1·
      2 months ago

      I made a honest effort, but in the end went back to Git for my personal projects. The advantages Fossil has over Git (wiki, bug tracker) are trivial to emulate with versioned plaintext files, and everything about Git’s version control system just clicks with my head. Having years of experience breaking and unbreaking things helps too.

      Tho one thing Fossil taught me is to merge by default, not rebase. Rebase when there’s good justification for it, and the rest of the time, have an alias for git log --oneline --graph --first-parent (or whatever that was). --first-parent collapses a horrible branchy-mergy history into a linear overview thereof, with details available when needed.

      • JackbyDev@programming.devEnglish
        0·
        2 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.)