Author Topic: approach to dedi console wrapper  (Read 2549 times)

idk where else this would go so i'm sticking it here

i'm working on a web panel-y thing for server management and i know a few people here have had experience wrapping the console

i would prefer a python-based approach but i can't quite figure out how to get subprocess and socket to place nice together.

i just need ideas based on the fact that the end application will be web output (and so ideas that include the best way to relay that would also be appreciated)

again idk about posting this here man sry

I used node.js for my web panel. There is a module for node.js called "child", which lets you control other programs with it. You can also pipe the IO Stream and read console lines. Not so much inputting lines (torque does some wonky console stuff so idk). An annoying problem with that though is it leaves a blank console window, with no console lines popping up into it, but rather in node.js.

You could try that, however, I lost my web panel a while ago when reinstalling PC.

I used node.js for my web panel. There is a module for node.js called "child", which lets you control other programs with it. You can also pipe the IO Stream and read console lines. Not so much inputting lines (torque does some wonky console stuff so idk). An annoying problem with that though is it leaves a blank console window, with no console lines popping up into it, but rather in node.js.

You could try that, however, I lost my web panel a while ago when reinstalling PC.
i'm gonna be doin stuff with node anyway so that'll probly be good

i ran into the blank window thing with python as well. console input doesn't matter as much since that can be handled within the simulation