✳flâneur — a map of the web's best reading

Using Git offline

gibbard.me · 1,019 words · saved by 1 readers

Some companies use an isolated network or even the complete lack of a network as a security measure to protect from unauthorized access. Working on these systems can be a struggle but it is still possible, and perhaps even more important, to use a proper version control tool like Git. By design Git works quite happily with no remote repository. You can branch, stage, and commit files just like normal. This works great if just a single machine is used for development, but this is often not the case. When security policy allows read/write access to a memory stick or portable hard drive a remote repository can be created on this device. On one development machine mount the memory stick. Navigate to the repository that is to be shared, add the remote repository on the memory stick, and push the changes. NB. The remote can be called anything. It doesn’t have to be called “origin”. Unmount the memory stick and mount it on another development machine. If the development machine does not have

Some companies use an isolated network or even the complete lack of a network as a security measure to protect from unauthorized access. Working on these systems can be a struggle but it is still possible, and perhaps even more important, to use a proper version control tool like Git. By design Git works quite happily with no remote repository. You can branch, stage, and commit files just like normal. mkdir testRepo cd testRepo git init touch test.txt git add --all git commit -m "Initial Commit" This works great if just a single machine is used for development, but this is often not the case.

Explore this link on the map →

saved by

related reading