Threads for hir0

  1. 1

    I think these kind of articles miss the point. It’s never been difficult to setup your own code hosting. 15 years ago many shared hosting services would even include Subversion and CVS hosting with web support for free as part of their hosting service.

    The problem is letting other people find, use and contribute to your project. For me personally, if a project isn’t on GitHub, BitBucket, or GitLab the chances of me even thinking about contributing are about zero.

    Obviously, that’s not important to everybody, but it’s something to think about.

    1. 1

      For me personally, if a project isn’t on GitHub, BitBucket, or GitLab the chances of me even thinking about contributing are about zero.

      Can you explain why that is? I’ve been thinking about self hosting projects vs using github, and am trying to think of specific weaknesses in the self-hosting option, or reasons it would deter would-be contributors.

      1. 1

        It’s a combination of laziness on my part and the fact that I don’t make many large contributions to other people’s projects. I have accounts on those services, and I know the generally accepted workflow for opening pull requests and getting changes submitted. The time from me saying, “Hey, this is a small bug I can fix,” to writing the code and opening a pull request can be as little as 5 minutes.

        But with somebody’s self-hosted Git repos, I don’t automatically know what the process is. Sometimes they’ll say, and sometimes they won’t, but it’s almost always more work than the third party hosts and it’s potentially different for everybody’s self-hosted code.

      2. 1

        My problem with GitHub at least is the fact that they inflict a double standard. They want everyone to open source their code, which I completely stand behind, while keeping a large proportion of their own codebase proprietary and closed. Not only that, but for the other two, the fact you have to pay for access to certain chunks of a service I host myself does not agree with me. If i’m hosting something, it’s all or nothing, not to mention they are all massively bloated and dependency-heavy

      1. 2

        Definitely not applicable to all use cases, but I realized at some point that I didn’t actually need a web UI for my personal git repositories, and have been much happier since I stopped trying to deploy them in favor of simply using ssh:// remotes.

        1. 1

          That’s true but it doesn’t make your code very accessible to outsiders and that seems to go against the spirit of free, open source code. True, it is possible to find the code still, but it makes it harder for someone to find.

        1. 12

          You basically copy-pasted the article I wrote from . The referenced link in your post is wrong (typo 2c30 -> 2f30). Booo!

          Here is the most up-to-date version (as linked from 2f30): . It has some notes to make cgit tarball snapshots working.

          A related article for git hosting:

          Edit: thanks hir0 for updating the article! It is totally fine now.

          1. 5

            I will admit I used a lot of the advice on your blog post to help me set up my server. I’m sorry it came across so copy-pasted. I’ve added a section to the top of the post to make it very clear that this post wouldn’t exist without your work. Also, sorry about the typo, that’s fixed now.

            1. 1

              Are you suggesting this is plagiarism?

              1. 3

                Quickly comparing the two, the submission is actually less helpful than the parent comment’s article, which says what stuff to install. The submission leaves that exercise to the reader.

              2. 1

                Just wanted to drop by to say thank you for writing that article. I’ve been running my own git server for a couple of months now.

                Now I only have to find one for setting up an email server ^_^.