I am currently using Digital v0.31. When running the GUI normally, I am able to enable and interface with its remote server. I am also able to see that the server is enabled in the .digital.cfg file in my home directory.
However, when I run the circuit in headless mode, via java -cp <path to Digital.jar> CLI run -dig <path to circuit>, the remote server does not seem to spin up.
Running a check of the bound ports on my machine also shows that the remote server port is not in use when using the CLI, whereas it does show up when I run the GUI normally.
Is this intentional, or a bug, or am I missing a step needed for me to control a headless instance in this way?
I am currently using Digital v0.31. When running the GUI normally, I am able to enable and interface with its remote server. I am also able to see that the server is enabled in the
.digital.cfgfile in my home directory.However, when I run the circuit in headless mode, via
java -cp <path to Digital.jar> CLI run -dig <path to circuit>, the remote server does not seem to spin up.Running a check of the bound ports on my machine also shows that the remote server port is not in use when using the CLI, whereas it does show up when I run the GUI normally.
Is this intentional, or a bug, or am I missing a step needed for me to control a headless instance in this way?