> Sometimes git pull fails halfway through because of network problems Separate the pull into "git fetch" into a shared bare git repository (if you care for ef

> Sometimes git pull fails halfway through because of network problems Separate the pull into "git fetch" into a shared bare git repository (if you care for efficiency) which is atomic and then a "git checkout" into a new directory using a single symlink(2) and rename(2) which is also atomic because rename is. > Imagine you’re pulling from git and at the same time, the app decides to import a module that changed profoundly since its last deployment. A plain crash is the best case scenario here. > On the other hand, deploying using self-contained native packages makes the update of an app a near-atomic, You can't have your cake and eat it too. Native packages have the exact same race conditions as an (inplace) git update.