4 ms·
I used to work on a team that was trying to adopt Docker. I was pretty much the sole developer of the frontend and one of the top active developers on the backe
by ngokevin 6y ago
I used to work on a team that was trying to adopt Docker. I was pretty much the sole developer of the frontend and one of the top active developers on the backend. It was really overkill to install an entire VM and spin up my computer fans to run a simple frontend webapp that was `npm install && npm run start`.
- gkcgautam 6y agoWhy not run it directly on the host machine during development, and run the docket image on the servers? This is the approach that I usually follow and it has worked fine for me so far. I need to build the Docker image locally only if something breaks down in the build pipeline.
- claytongulick 6y agoDoesn't that sort of kill one of the main selling points of using docker in the first place? Consistent environment on local, test and prod servers?
- comprev 6y agoI think they meant using a remote development server instead of spinning up a VM locally. There was a post a few days back about using a NUC as a powerful remote (over LAN) development server
- ngokevin 6y agoWell, their selling point was that it was easier to develop on locally. We weren't even running Docker in production.