Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SpineDBServer as standalone application #431

Open
soininen opened this issue Jul 12, 2024 · 0 comments
Open

SpineDBServer as standalone application #431

soininen opened this issue Jul 12, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@soininen
Copy link
Collaborator

soininen commented Jul 12, 2024

SpineDBServer is a socket server that can be used to communicate with spinedb_api over a network socket. When using the server, client processes can access Spine data without the need to call Python. Most notably, SpineInterface does not need PyCall when accessing Spine data via the server.

Toolbox sets up the server for Julia Tools such as SpineOpt automatically. However, when running SpineOpt outside of Toolbox e.g. for development purposes, PyCall is required and it is notoriously difficult to set up. If it was possible to start SpineDBServer as a standalone server, SpineOpt users would not need to use PyCall even in this situation.

We could add an entry point to spinedb_api that starts SpineDBServer process. It should accept a database URL, network port and filter settings as command line arguments. You could then start the server manually or add suitable commands to e.g. run_spineopt.jl script to establish a connection.

@soininen soininen added the enhancement New feature or request label Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant