|
|
|
|
|
by swaggyBoatswain
3030 days ago
|
|
shouldn't you be putting your code repositories in something like c:/www folder, and using purely git to track it? There's lots of 3rd party solutions for .dropboxignore personally I've used many of them and am not a fan of it (perl scripts, 3rd party apps, etc). I wish dropbox would natively implement .dropboxignore, but its probably never going to happen since only a small % of users voice their concerns for it. Average dropbox user probably doesn't care or doesn't know what a .dropboxignore is. |
|
Also dropbox's 30 day version history did save me a couple times when I accidentally deleted something before committing. And not having to worry about losing the day's work even if your computer fails is good for peace of mind.
That said this hits a lot of edge cases with dropbox syncing since it's not built for this kind of workflow. Every time you do npm install it will cause thousands of files to sync. I have had the .git folder get corrupted when I start using it before it has fully synced. Or git would handle syncing internal symlinks/permissions/casing differently and I would need to rely on git to restore.