4 ms·
So in that model, you have to ship your codebase into the VM and then work on it from there. If you're git-managed now you're having to either ship your git cre
by rtpg 5y ago
So in that model, you have to ship your codebase into the VM and then work on it from there. If you're git-managed now you're having to either ship your git credentials into that VM to push stuff up, or you're like having to figure out how to ship the codebase back to the host when you need to.
The whole "magic" is that you work on the files on your host machine! I think VSCode is doing god's work (along with other tools) to make remote editing a nicer experience, but well... I use Docker on Linux and just edit files locally. It's nice!
- allendoerfer 5y agoAt this point you can just use Vagrant again and skip using Docker.
- FooBarWidget 5y agoVagrant also has filesystem performance issues. VirtualBox host directory sharing is awfully — unusably — slow, even more so than the old Docker Desktop mount. Vagrant takes a lot more disk space and RAM. VirtualBox isn't as efficient as the macOS hypervisor. And every Vagrant project is a separate VM, instead sharing the same VM for multiple projects.
- towawy 5y agoGit credentials are not a huge deal if you use ssh keys. You can forward your local ssh identity to the VM / remote host by adding these options to the Host entry in you ssh config: IdentitiesOnly yes AddKeysToAgent yes ForwardAgent yes