You already have a Git server (opens in new tab)

When I started using Git around 2006, we didn't have GitHub. We used Google Code for SVN hosting, but we wanted to try Git because it was 'truely' decentralized, so we just pulled from other developers' computers directly. It involved setting up port forwarding on the router and letting your computer on 24/7. Fun times.

You can also have an upstream git repo on a local filesystem and add that as a remote.

But when most people talk about a git server that includes collaboration and giving people SSH access just so that they can read from your repo is not reasonable.

This is indeed a Git server. It is not a Git Forge though. Pull Requests, Issues, CI/CD, access management, etc. are about as important as a putting my code somewhere.

Huh, I've always set up bare repos as my "local" (on a desktop somewhere in my house) destination. I didn't realize you could just use regular repos.

> This is a nice way to work on server-side files without SSH lag or error-prone copying.

Are people really copying files to the servers then committing there?

This is an AI generated article

I find it strange the websites some of these HN articles are hosted on... going through the effort to write a post before getting a domain outside of .vercel.app is interesting.

Can you rewrite this by hand, please? I was so confused what this article was supposed to tell me.

> No YAML file with 47 indents.

What is this referencing? what yaml file?

The front-end also screams AI generated

Looks like a bot doing self-promotion.

> That is it. No Docker. No CI pipeline. No serverless function. No YAML file with 47 indents. Just SSH and git — two tools you already have.

Sigh.