Does syncing the .git repo between computers cause an issue?

user2211907

I have a setup where the entire projects folder is synchronized in real time across several computers (think something like Dropbox). Inside that folder I might have an individual project folder like project-A. Then inside the project folder I always have source and documents folders.

I want to keep the source folder under version control, but not the documents. So I clone my sources into the source folder. This means that my local git repo will be synced across multiple machines (possibly both Linux and Windows).

Is this going to cause problems and screw up my git repo in some way I am not aware of? I don't know if I can disable the syncing of the source folders, and even if I could, someone else might forget to do that and have problems. I've thought about separating the source and documents into separate root folders where only one of them is synced, and the other isn't, but I would really like to keep all of the project files in one folder if possible.

Any ideas on the best way to do this?

[edit] For clarification, the git repo is cloned from Kiln (online git repo), but it just so happens that the location is is cloned it is synced across multiple computers.

Drew Stephens

I've kept my code checkouts in Dropbox now for 5 years writing code most every day. I use this to sync these changes between my desktop and laptop. This includes doing large refactorings that change dozens of files at a time.

Very rarely I have encountered problems, though they have a couple of times been severe (a corrupted repository) so you need to push early and often. Those rare problems are well worth the incredible convenience of being to continue work from right where you left off when switching between machines.

I've also tried this with Transporter with much, much less success. The Transporter file watcher doesn't seem as good, which led to conflicts every few weeks. Additionally, the syncing is much slower—whereas Dropbox seems to get things matched within a few seconds if both machines are up on the same network, Transporter had a median time of 30 seconds, but sometimes up to a few minutes.

Collected from the Internet

Please contact [email protected] to delete if infringement.

edited at
0

Comments

0 comments
Login to comment

Related

From Dev

share git repo between two computers locally

From Dev

Syncing git repositories across computers

From Dev

Syncing Windows registry between several computers

From Dev

Syncing Large Amounts of Files Between 2 Windows Computers

From Dev

Windows file permissions/ownership are preventing me syncing between computers

From Dev

Syncing apt-get installations between multiple computers

From Dev

Build Error while syncing the Git repo: Illegal characters in path

From Dev

Syncing repo problem

From Dev

Syncing branch with upstream repo

From Dev

Does Google Chrome sync history between computers?

From Dev

Load git repo with composer - autoloading issue

From Dev

How can i find issue cause in git?

From Dev

Outlook calendar Syncing issue

From Java

git: diff between file in local repo and origin

From Dev

What specifically does the AOSP repo tool checkout for each git repo?

From Dev

Does computers on same LAN share their hosts file between each others?

From Dev

How does communication between 2 computers in a single network happen?

From Dev

Does file user ownership change when transferring files between computers?

From Dev

How does Http server distinguish between computers behind a router

From Dev

Does syncing work for calendar?

From Dev

syncing UIPageViewController with UISegmentedControl logic issue

From Dev

pouchDB to iriscouch syncing issue with remove

From Dev

git clone issue: repo too large? (50m)

From Dev

Yet another "how to rebase one Git repo onto another" issue

From Dev

Issue with require gem, when passing git-repo to gem in Gemfile

From Dev

Syncing forked repo with upstream/master or upstream/develop?

From Dev

repo: stuck while syncing (also with -f)

From Dev

I want to fork a repo, add a feature and keep syncing with original repo

From Dev

Does not calling Future.get cause any issue?

Related Related

  1. 1

    share git repo between two computers locally

  2. 2

    Syncing git repositories across computers

  3. 3

    Syncing Windows registry between several computers

  4. 4

    Syncing Large Amounts of Files Between 2 Windows Computers

  5. 5

    Windows file permissions/ownership are preventing me syncing between computers

  6. 6

    Syncing apt-get installations between multiple computers

  7. 7

    Build Error while syncing the Git repo: Illegal characters in path

  8. 8

    Syncing repo problem

  9. 9

    Syncing branch with upstream repo

  10. 10

    Does Google Chrome sync history between computers?

  11. 11

    Load git repo with composer - autoloading issue

  12. 12

    How can i find issue cause in git?

  13. 13

    Outlook calendar Syncing issue

  14. 14

    git: diff between file in local repo and origin

  15. 15

    What specifically does the AOSP repo tool checkout for each git repo?

  16. 16

    Does computers on same LAN share their hosts file between each others?

  17. 17

    How does communication between 2 computers in a single network happen?

  18. 18

    Does file user ownership change when transferring files between computers?

  19. 19

    How does Http server distinguish between computers behind a router

  20. 20

    Does syncing work for calendar?

  21. 21

    syncing UIPageViewController with UISegmentedControl logic issue

  22. 22

    pouchDB to iriscouch syncing issue with remove

  23. 23

    git clone issue: repo too large? (50m)

  24. 24

    Yet another "how to rebase one Git repo onto another" issue

  25. 25

    Issue with require gem, when passing git-repo to gem in Gemfile

  26. 26

    Syncing forked repo with upstream/master or upstream/develop?

  27. 27

    repo: stuck while syncing (also with -f)

  28. 28

    I want to fork a repo, add a feature and keep syncing with original repo

  29. 29

    Does not calling Future.get cause any issue?

HotTag

Archive