Actually I have implemented the docker approach earlier , but for front-end development I found it of no practical usage. Because in front-end we are mostly dealing with browser , styling and dockers are more deployment oriented and not development oriented and even though having your platform os separate from base os is a good development practice but if you have those services you can dockerize that services and consume them in the frontend development environment as locally available api endpoints also as dockers are process so it's better to use them like that only. You can dockerize your build system , probably attach jenkins with docker to create a build platform for your frontend application. But it's best to use them in a separate cloud system than your own system. Eventhough deploying dockers are super simple but the whale eat's a lot if you don't know what and how to manage.Secondly you will need to tell the devs to configure their machines for local development , because dockers are not vm's. People working with docker will realize what I mean.
I had the same exp trying to isolate my dev env locally with docker and mini-kube. You have to install, configure, manage them, spend your disk space, memory and CPU cycles on running it. It is better when these techs are just implementation details sitting in the cloud. For example, as Gitpod allows develop dev.to itself from browser: dev.to/ben/spin-up-a-local-instanc... Setup is automated with Docker image launched in the cloud but you don't need to care about it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Actually I have implemented the docker approach earlier , but for front-end development I found it of no practical usage. Because in front-end we are mostly dealing with browser , styling and dockers are more deployment oriented and not development oriented and even though having your platform os separate from base os is a good development practice but if you have those services you can dockerize that services and consume them in the frontend development environment as locally available api endpoints also as dockers are process so it's better to use them like that only. You can dockerize your build system , probably attach jenkins with docker to create a build platform for your frontend application. But it's best to use them in a separate cloud system than your own system. Eventhough deploying dockers are super simple but the whale eat's a lot if you don't know what and how to manage.Secondly you will need to tell the devs to configure their machines for local development , because dockers are not vm's. People working with docker will realize what I mean.
I had the same exp trying to isolate my dev env locally with docker and mini-kube. You have to install, configure, manage them, spend your disk space, memory and CPU cycles on running it. It is better when these techs are just implementation details sitting in the cloud. For example, as Gitpod allows develop dev.to itself from browser: dev.to/ben/spin-up-a-local-instanc... Setup is automated with Docker image launched in the cloud but you don't need to care about it.