Closed valeedmalik closed 3 years ago
2 possible workarounds to this:
You can try to start the engine manually via command-line, and connect to a custom process:
Also the port is randomized at the first run will stay the same during the entire IntelliJ session, so you can re-setup container once per day 😄
Yep have been operating via method 2. Was just hoping for a more direct approach!
I might be missing something however every time I trigger pycrunch-engine via IJ, it will start it on a random port. I am working with Django out of a container where I need to specify port to open on the container to connect to the engine. Currently I'm making an exec call into the container and starting pycrunch-engine on 5000 and have my container open at the same.
Would you know of a work around for this? Would like to utilize start/stop of engine from IJ.