On Fri, Aug 25, 2023 at 09:54:02AM +0200, Loris Bennett wrote:
Does a bare remote to which you simply push not already provide you with an adequate backup? One you have made a number of commits, you can just push them to the remote.
I am old and my fingers sometimes strike the wrong keys. (In younger days, I was a very skilled typist.) And now and then, I manage to make an entire paragraph or more disappear. So, whether backups are manual or automated, my rule is (1) commit frequently, and (2) backup with each commit.
However, I may have missed some of the intricacies of your scenario. You seemed to imply that you don't have a bare remote, which I find surprising.
I also have old computers (with old drives). Moreover, I live out in the country where power interruptions are common (thus, I power a computer through a UPS). These two factors are why I wish to have a backup repository on a separate computer. --- 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. 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. If pushing from PRODUCTION is more reliable or less trouble-prone than pulling from BACKUP, kindly explain to me, and I shall change. If a bare BACKUP is more reliable or less trouble-prone than a non-bare BACKUP, kindly explain to me, and I shall change. RLH
