3 ms·
While I agree that this sort of workflow keeps development environments reproducible, I disagree with freezing editing tools like this. Nothing about your proje
by mid-kid 4y ago
While I agree that this sort of workflow keeps development environments reproducible, I disagree with freezing editing tools like this. Nothing about your project should require specific IDEs or similar software. Like you said, less complexity is easier to make more reliable, so stick to purely the tools necessary to build and run the software, rather than including the tools to edit it.
If I need a VM for things, I typically start a small rsync or ftp server on the host so the VM only has to mirror the files, build and run.
- namaria 4y agoAbsolutely. I am not installing VSCode on production VMs, the step I described is purely for setting up a portable developer environment. Then instead of telling other developers to install a laundry list of tools I can just give them a copy of my VM. Throw in something like Vagrant and it's easy to share a standard work environment. Then to roll things into production it's another game.