Regarding git hostingPublished on 2020-08-28 by flewkey
When it comes to online services, many people look past simple solutions and jump to the large pieces of software and complicated solutions. One case of this which I see on a regular basis is git hosting, and I don't think that most people understand how simple it is to host git repositories.
Many people think that hosting git is hard because they believe that it's
necessary to install and configure a code forge on their server. They will
usually install GitLab, which is
and definitely not overkill for hosting a handful of personal repositories.
There are also a few people who install less
git services like Gitea and SourceHut
to host their projects. The thing is... they really don't have to.
git clone --bare repo repo.git && scp -r repo.git name@server:/srv/git
Those are the only commands needed to run to host a git repository on any server
with SSH access. The path doesn't even have to be
/srv/git. As long as the
ssh://name@server:/srv/git/repo.git) points to a bare git repository
which the user has read access to, they can pull from it. With write access,
they can even push to it. Amazing.
For more information on using git with your server, read the relevant chapter from the Pro Git book. It will explain how to set up a more limited "git" user for SSH, use the git daemon, rig up git-http-backend on your webserver, and even use GitWeb to show a web UI. It's not much harder the simple setup above.
There are also other projects which can compliment git hosting. If GitWeb isn't fancy enough, there is also cgit. Issue tracking can be handled with Trac, and e-mail can be used to accept patches. At that point though, using a proper code forge might be a more suitable option.
Self-hosting git really isn't that important, nor is there anything wrong with sticking all of one's projects on GitHub. (Most of mine are on the SDF GIT Society anyways.) However, I've seen too many people purchase subscriptions from GitHub for the privilege of private repositories. I'm tired of seeing unused GitLab and Gitea instances as well. When setting up a code forge, make sure that it's necessary.
Articles from blogs that I like
GitHub took a note out of the Microsoft “EEE” playbook when designing their git services. They embraced git, and then rather than building an interface on top of email — the collaboration mechanism that git was designed to use, and which is still used for Li…
From Blogs on Drew DeVault's blog
Published on August 27, 2020
So today I attempted to use C#, my opinion of it has converged with my previous opinion all those years ago. C# is a complete piece of shit that sucks all the life out of coding. Doing anything in this … Continue reading →
From DeadFish Shitware
Published on August 25, 2020
This is a post I've been meaning to write for a while now: one anecdotally comparing programming languages in the Lisp family. I consider myself to be a Lisp hacker. Perhaps that much was obvious from the letter λ adorning my website's header, a refe…
From Jakob's Personal Webpage
Published on January 1, 0001
Generated with the spectacular power of openring