6 ms·
I would observe that with DVCS, if your hard drive crashes you can still lose several days of unpushed code, too. I recommend and use cron jobs to push and/or r
by jerf 15y ago
I would observe that with DVCS, if your hard drive crashes you can still lose several days of unpushed code, too. I recommend and use cron jobs to push and/or rysnc things around on a more frequent basis for my really important stuff.
- deleted 15y ago[deleted]
- gujk 15y agoYou could buy a second hard drive and put it behind your other drive and occasionally copy important files from your front drive up to your back drive.
- BonoboBoner 15y agoOr use TimeMachine if you are on a Mac.
- wizard_2 15y agoNo, if TimeMachine screws up a file it stays screwed up for ever after every backup, there's no integrity checking. It also completly barfs on large files that change little by little. The best example of that is the entourage mail store, but any single file db will do. I've seen clients bit bad by these problems. Don't get me started on the time capsule...
- vidarh 15y agoWorks great until your computer/home/office catches fire. Personally I have a mirrored drive set that I use as my primary storage, and a third disk that I rsync to nightly and use for backups of other stuff, because I don't trust that I won't have filesystem errors or controller problems that might render both disks in the mirror unusable. Then on top of that I use Crashplan to ensure I have an offsite copy. For most of my code I also push to github or private external repositories regularly and/or pull to my laptop. Maybe a bit paranoid, but I've had to recover from enough scary hardware and software failures over the years to not want to take risks.
- run4yourlives 15y agoDropbox fixes this.
- ori_b 15y agoRaid and rsync are your friends. Use them.
- xutopia 15y agoWhat's wrong with a remote branch you push to and then merge back into master afterwards?
- jerf 15y agoWas my second sentence really that incomprehensible?
- scottschulthess 15y agoThis is why I keep my working copies in Dropbox
- GoldenMonkey 15y agosecond that... my working folders are dropbox... and commit to cloud git repository as needed.
- kellishaver 15y agoSame here. I had some sort of electrical problem with my last computer and lost my hard drive due to it. Unfortunately, my back-up drive was also plugged in at the time and it got fried, as well (really bad luck/timing there). One of the first thing I did when I got the new computer was to put a symlink to my projects directory in my Dropbox folder, so that all of my projects now get backed up to Dropbox automatically.
- tl 15y agoWe keep our main repository in under dev/$PROJECT and backup repositories under user/$USERNAME/$PROJECT. Then we set a post-commit hook to push to the backup server on commit. Setting up the backup and creating the hook is done by a shell script you run after cloning.
- swah 15y agoI'm always doing git push origin develop for this reason, but some environments probably don't allow you to do this easily? I work alone. (EDIT: be nice to people)
- ConstantineXVI 15y agoWe typically work in personal feature branches before merging into develop; if you use a similar workflow there shouldn't be much issue at all from pushing constantly.
- swah 15y agoCan you protect from other folks pulling it? Sometimes people just don't want to reveal their code while is ugly...
- ConstantineXVI 15y agoGitolite[1] will let you mark branches as private on the remote either by specific branch name or a regex (ex: any branch that starts with "swah-" is private to you) if you want privacy before revealing your code. [1] http://sitaramc.github.com/gitolite/ http://sitaramc.github.com/gitolite/