3 ms·
I am building my Docker images with a local Docker daemon, push them to a private registry and run "kubectl apply" to refresh the deployment afterwards. Where d
by fredamot 8y ago
I am building my Docker images with a local Docker daemon, push them to a private registry and run "kubectl apply" to refresh the deployment afterwards. Where does your tool fit in my workflow? Maybe I am not getting the full idea but I don't see the benefit...
- gentele 8y agoThat is a very common flow today but re-building and re-deploying images on every change takes a lot of time and you cannot use modern dev features such as hot reloading (e.g. with nodemon). With the DevSpace CLI, however, you can simply build and deploy once and every following code change will only lead to a code synchronization. The DevSpace CLI will sync your modified source code files straight to your containers running remotely inside a Kubernetes cluster. You can use hot reloading (e.g. with nodemon) and still build and run everything entirely on a remote Kubernetes cluster. Only when you change your Dockerfile, the DevSpace CLI will rebuild and redeploy your container images. This saves a lot of time during development. I hope you will find the time to try it out and give us feedback on the project :)
- fredamot 8y agoThanks for your explanation. I have tried it with nodeJS, the sync feature is really great. But I can't get the debbuger to work, I am using VS Code. Can I even use the debugger?