can we support export()-ing to a remote orca server?

It looks like the orca_serve() function starts up a server and returns a method that I can use to export a graph to the server.

What if I already have a server running on another machine? I would like to be able to export a graph to that already running server without starting a new server.

The reason I ask for this feature: I want to export my graph inside of a Shiny app that is deployed in a containerized environment. Both my app and orca have really big dependency trees and I have spent a lot of time (so far unsuccessfully) trying to build a Docker image that can support both my app and orca.

If this feature existed, I would not need to create a new docker image. I could use the off-the-shelf orca container. I could use docker-compose to start up both my app and the orca server, and then in my app I could submit to the running orca server.

Is this something you would be interested in supporting? I imagine orca_serve() with a couple extra arguments, like hostname="localhost", start_server=TRUE which I could override to point to an already-running server on another host.

Start with the orca_serve() function and the export method it returns, then trace how the current server is started and contacted. Define the change around exporting graphs to an already-running remote Orca server without starting another server, including the Shiny and Docker Compose use case described here.