1–6 of 6 posts
I understand there are tools to improve this workflow (Vagrant+Puppet), but I am curious to hear what other dev environments/workflows look like or work for others.
Alternatively, you can code directly on the VM and use an editor that lets you do remote editing (vim, emacs, sublime text ...).
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 ...).
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 ...).
So when would be a good time to start using git - perhaps when the project is deployed into beta?
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.
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 ...).
So when would be a good time to start using git - perhaps when the project is deployed into beta?
(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.