Open blakeembrey opened 8 years ago
Thanks for the feedback @blakeembrey! I've been thinking about different architectures for handling cluster mode and or workers. Decoupling the child from the dashboard would allow for greater control but would create challenges for stdout
, as you note. Leveraging the existing infrastructure in cluster might solve some of these problems.
https://github.com/chjj/blessed certainly has support for input and multiple screens so it'd just be a matter of coming up with a reasonable design.
Once I have some spare cycles I'll look into prototyping a few different approaches.
Really nice work! I'm just opening this issue to submit an idea.
For applications that maybe have multiple processes running, what do you think about enabling tabs? Perhaps each application running could register itself to a display name and you could toggle between them using numbers. I could imagine spawning child processes that might render a new tab and then when it closes the tab disappears. Also for use with projects like https://github.com/strongloop/node-foreman, where you might have two process (web/worker) running and want to run them together.
Some ways it may work:
child.stdout
approach (it might need to monkey patching process stdout instead)nodejs-dashboard --new-tab web
that'll use the parent dashboard process to attach to it (this would likely mean a new tab results in two tabs - one for the overall process, one for the new tab child)