3 ms·
I diaagree on some points: github/git is not an appropriate backup strategy and github is not user friendly enough for non technical people (the default reposi
by johnchristopher 12y ago
I diaagree on some points: github/git is not an appropriate backup strategy and github is not user friendly enough for non technical people (the default repository page, github pages is another matter).
- acdha 12y agoDo you have any support for those assertions? In particular, the backup claim is rather dubious unless you're redefining “backup” to be a much higher bar than most common answers meet.
- johnchristopher 12y agoGit is a distributed revision control system and designed as such. The fact it can be used as a back-up tool doesn't mean it should be used as a back-up tool, especially when there are back-up solutions designed from the ground to do just that.
- acdha 12y agoBut what you actually said was “Github/git is not an appropriate backup strategy”. Git is tamper-evident and uses strong hashes to protect against bitrot, has full change tracking and numerous measures to avoid data-loss becoming permanent if you detect human error before weeks/months go by, has integrated remote tracking so you can tell how stale your off-site copies are and trivially update them, and most server implementations allow as much access control as you desire. Assuming that we're talking about things which are already stored in Git and not e.g. an HD video collection, what would make your original statement true?