You already have a Git server (maurycyz.com)

Article summary

The article explains that having a git repository on a server with ssh access is sufficient to use git remotely, allowing for cloning and pushing changes without the need for a separate git server. This setup can be used for server-side file management and can also be configured to run a shell script when a new push is received. The author finds this setup convenient for managing their blog's site generator and appreciates the automatic backup feature. This approach leverages the decentralized nature of git.

Main themes

• Git remote access
• SSH and git
• Decentralized version control
• Server-side file management
• Git basics and misconceptions

What commenters say

• Many people mistakenly believe that git is equivalent to GitHub, highlighting a lack of understanding of git's decentralized nature.
• Some argue that it's not surprising that people conflate git with GitHub, given how they were taught or introduced to version control.
• Others point out that relying on hearsay or incomplete knowledge is unprofessional and that engineers should strive to learn their craft properly.
• There is a disagreement on whether the observation that many people think GitHub is git is a sign of a larger problem with education or just a common misconception.
• The use of ssh for git remote access is not widely known, even among those familiar with git, and is a powerful feature of the version control system.
• Some commenters share anecdotes about IT and security teams making decisions based on misconceptions about git and GitHub, highlighting the need for better understanding.
• The discussion touches on the idea that git's support for multiple transport protocols, including ssh, makes it a versatile tool for version control and collaboration.
• There is a concern that a growing misconception about git among software development and operations professionals could have negative consequences.