Open 0xIslamTaha opened 5 years ago
That's really not how things are supposed to work. container running an flist are meant to be used in production. When someone develop template it shouldn't run the robot in an flist, this makes everything so much more slow and complex.
Also what you propose is already possible today if the 0-os is running with development
or support
flag.
So we could maybe develop some tools to make this easy, but also devs should learn how to develop things properly.
Also if you are debuging stuff in production, then we need to use the right tools, like logging etc. putting a break point on a production node is just wrong
My use case is not developing a new template nor debugging in a production mode. My use case is I have a running code in my zos developing a machine which is running by default a zrobot container and I need to debug the js code to detect the bug root cause. If u have a way to do that in development mode, please share it
https://github.com/threefoldtech/home/issues/115 could be a way to solve this problem. Having an on demand tty forwarding of the logs of your applications
The existing version of the code could already be used to do that I think. We can check how to deploy that to get interactivity.
as all zos nodes are running a zrobot server and using js code via a zrobot container, we need a way to debug those codes.
The first problem is zrobot flist doesn't have an ssh component and the second problem is, even if it has we cant walk through the running zrobot process.
I suggest creating a zrobot development flist which has ssh and running the zrobot process inside a tmux window