On Fri, Aug 25, 2023 at 10:36:33PM +0000, Russell L. Harris wrote: > As best I understand it (and kindly correct me if I am mistaken), a > bare repository is a central repository used by a group of developers. > Each developer has his own repository, and no developer ``owns'' the > central repository.
The number of developers in the group may be 1. Ownership is not relevant, really. That's just politics, and is outside of the technical discussion. Even if you "own" both the central repository and the working repository, and if you are the only developer with access to the central repository, then you're still following the same basic technical setup. > But for me, the only purpose of the backup repository is to ensure > against data loss due to a catastrophic event such as drive failure on > my production host. The basic setup that has been described is perfectly suited to this scenario. Arrange it so that when you run "git push" in your working repository, it sends your commits to the central repository. (There may be a prompt for your password or your passphrase, depending on how you've configured ssh to the remote system.) That's basically all you need to do. Everything else is just needless complexity.
