3 ms·
>If I just need a git repository, I store it locally. Git is a DVCS for a reason -- most single person projects don't need a remote anyway. I use a remote as a
by Nadya 8y ago
>If I just need a git repository, I store it locally. Git is a DVCS for a reason -- most single person projects don't need a remote anyway.
I use a remote as an easier-to-maintain-and-test backup than trying to maintain a mirrored local repository on another drive.
- Shank 8y ago> I use a remote as an easier-to-maintain-and-test backup than trying to maintain a mirrored local repository on another drive. You should really consider getting a good backup solution, like Tarsnap or Backblaze, to follow from the "two is one and one is none" principle of backups. That is, if you haven't already.
- Nadya 8y agoI already use Backblaze as it's important to have off-site backups whenever possible. However, needing to wait several weeks to download my data is not always an option. I'm a digital hoarder and by that I mean I have >30TB of data. My backup solution for most things is 3 local copies and 1 remote copy. Files I don't deem important enough to pay to store 3 times locally aren't backed up locally but still are backed up with Backblaze. Some things are easier to entrust to someone else (eg: git repos) than trying to maintain local mirrors. Also a Backblaze backup of a git repository doesn't do me much good if I want to quickly grab it (talking minutes to download from Gitlab instead of hours/days from Backblaze) so it makes more sense to use Gitlab as a remote so I can quickly grab it if I lose my local copy. All of that aside, it's still easier to maintain-and-test a remote repository than to maintain-and-test local repositories.