3 ms·
Why don't you keep your bare repo in Dropbox and work in a clone outside? This way you wouldn't have build artifacts syncing. Just push after committing and pul
by mpanta 9y ago
Why don't you keep your bare repo in Dropbox and work in a clone outside? This way you wouldn't have build artifacts syncing. Just push after committing and pull from other machines. If you work alone you don't risk conflicts.
Or maybe even better, use Keybase.io encrypted git private repositories. They are free.
- superasn 9y agoAll my projects have .git directories inside them too. So creating a .git in top directory makes them submodules. To fix that right now i'm using a mercurial repo for the top directory and .git inside my project dirs (since BitBucket supports both). This works for now but it's not automatic like Dropbox and there are size limitations. So just wondering what the most elegant solution is.
- mpanta 9y agoJust to be sure I have understood correctly, this is to have your different projects synchronized all at once, right?
- superasn 9y agoYes that is correct
- mpanta 9y agoMaybe than something like google Repo could be of help? Or maybe even a custom script using rsync to/from Dropbox with appropriate exclude options. Probably using something similar to what's described in https://unix.stackexchange.com/a/168602 https://unix.stackexchange.com/a/168602 or even better using git ls-files -i to get the ignore list (https://git-scm.com/docs/git-ls-files https://git-scm.com/docs/git-ls-files).
- vfulco 9y agoWhat OS are you using Keybase.io on? I tried to install latest version on Unbuntu 16.04 and it gave my error. Then I read something about messing with .ssh dir and I didn't proceed. I had a Go setup tool trash all my paths last year. Chastened from experience. TIA.