[HN Gopher] Developing inside a virtual machine
       ___________________________________________________________________
        
       Developing inside a virtual machine
        
       Author : disintegrator
       Score  : 31 points
       Date   : 2024-12-29 17:51 UTC (3 days ago)
        
 (HTM) web link (blog.disintegrator.dev)
 (TXT) w3m dump (blog.disintegrator.dev)
        
       | moritonal wrote:
       | Thr Dev Container ecosystem for VsCode really is quite impressive
       | at the moment. All your dev dependencies, wrapped up in a docker
       | image per repo.
        
       | jareklupinski wrote:
       | is there a way to forward usb/serial ports from my local machine
       | to the dev container?
       | 
       | maintaining consistent firmware development environments using
       | containers is a great idea, and current solutions involving
       | proxying the compiled binary work well for flashing quickly, but
       | switching back and forth between UART and Serial Debug is always
       | more convenient when the IDE can handle it all
        
         | nottorp wrote:
         | I've done linux/arm yocto development from VMs. The best
         | solution to pass usb/serial was still VMWare the last time I
         | had to.
        
       | amelius wrote:
       | Beats developing inside a docker container.
        
       | mongol wrote:
       | I do something similar but using WSL on Windows. But something I
       | really, really hate is dealing with special certificate handling
       | required to pass the corporate Zscaler proxy. I think it works
       | somewhat transparent on the Windows host, but repeating the setup
       | in every VM is such a pain.
        
         | chrisweekly wrote:
         | Given how much you hate it, any chance you documented how you
         | did it?
        
       | dsfsaff wrote:
       | I have used a Virtual Box VM with a Ubuntu guest for years and it
       | has worked great. It's as close to the VM's in prod you can get.
        
         | malux85 wrote:
         | I used to do that, but now that all of our microservices are
         | dockerized every microservice has its own docker container
         | 
         | Vscode supports remote containers, so everyone in the org just
         | develops INSIDE a replica of the prod container
         | 
         | All containers run remotely on enormous machines with 800+ GB
         | of RAM and 8+ GPUs
         | 
         | It's trivial to share environments now because you just open
         | the project and the dev container starts up and installs all
         | the deps, devcontainer.json is just a few kb so just check it
         | into git
         | 
         | Engineering, DevOps, Data science all use this setup, push
         | around your devcontainer.json and everyone gets the same GPU
         | accelerated dev environment with near unlimited RAM and
         | hundreds of CPU cores, none of this hardware is local so you
         | can code on the balcony/beach on your MacBook Air, light and
         | easy to travel with.
         | 
         | We put VMs in the same country as our staff so latency has
         | never been an issue
         | 
         | This is the dev setup I've wanted for ages, and it's a joy to
         | use
        
       | mrbluecoat wrote:
       | If you like NixOs and virtual development environments, perhaps
       | try https://www.jetify.com/devbox or https://flox.dev/
        
       ___________________________________________________________________
       (page generated 2025-01-01 23:00 UTC)