News for hackers. Stuff that matters.
Re:Ask HN: Dev Environments and Workflows by AlexeyBrin on Thursday October 09, 2014 @10:38AM (#8432597)
Try rsync you could bypass 2 and 3. Basically, every change you made on your desktop can be automatically synced with the VM.

Alternatively, you can code directly on the VM and use an editor that lets you do remote editing (vim, emacs, sublime text ...).

Re:Ask HN: Dev Environments and Workflows by taurenk on Thursday October 09, 2014 @10:40AM (#8432608)
So when would be a good time to start using git - perhaps when the project is deployed into beta?
Re:Ask HN: Dev Environments and Workflows by swah on Friday October 10, 2014 @09:10AM (#8437464)
You could use Git right now, but not to transfer code to the VM and compile. Its a system to version [1] your code.

(Although I mostly skip using Git in toy projects, and just backup to Dropbox).

[1] If you push your changes to some offsite remote like Github, you are also backing up your code.

Re:Ask HN: Dev Environments and Workflows by AlexeyBrin on Thursday October 09, 2014 @10:46AM (#8432649)
You could use git from the start if you wish, this will keep a history of how your code evolved and you will also be able to use an older version of the code if necessary.

My suggestion was that it is faster to code directly on the VM or use rsync, than to push code on GitHub and pull it on the VM.