this is unfortunately, an unfixable issue. A big downside to my setup is that you can either configure, or run. Once you are running you need to stop the process to configure. I have tried a variety of fixes to this issue but to no avail :(
Here is what I have tried
pexpect (did not work)
Threaded process polling (did not work)
subprocess (did not work)
However, I have an idea that I think may just work, though it is rather hacky
Global
Implement more CLI control (such as starting by managing a certain server)
Also with (crss -s ): Show a ttymessage such as "go to TTY ## to run commands"
On Windows
When you click start, and if the setting is on, automatically open a new window to that server's configuration
On Linux
If in a display, do the same as Windows. In TTY it will be harder. It will need to
Get the TTY number
Find an empty TTY
Initialize config process on empty TTY with message "go back to x to run commands"
Change to new TTY
However there is a major problem and that is what if the user forgets what TTY the config console is on.
I've come up with a new solution. For Windows we will use the old one For Linux, the server will be started in "screen." From there, commands can be sent easily
this is unfortunately, an unfixable issue. A big downside to my setup is that you can either configure, or run. Once you are running you need to stop the process to configure. I have tried a variety of fixes to this issue but to no avail :( Here is what I have tried
However, I have an idea that I think may just work, though it is rather hacky
Global Implement more CLI control (such as starting by managing a certain server)
Also with (crss -s ): Show a ttymessage such as "go to TTY ## to run commands"
On Windows When you click start, and if the setting is on, automatically open a new window to that server's configuration
On Linux If in a display, do the same as Windows. In TTY it will be harder. It will need to
However there is a major problem and that is what if the user forgets what TTY the config console is on.