PROJECTS: helen
CHANGESET: create new component/module
DESCRIPTION:
An isolated task that does not require any knowledge of the project internals.
Currently, to set up the whole qua-kit environment, one has to run separately: qua-server, helen, and all helen services (at least siren and one more computational service). This is not so convenient, so I propose to let helen itself start the services she is aware of.
The changed helen pipeline as I imagine it:
helen starts as usual and from time to time executes a special function (maybe in a separate thread)
- This function checks a special folder. For example,
bundledServices subfolder w.r.t. helen executable.
- The folder contains some (arbitrary) files + a set of
service-name.yml files. Each service-name.yml file contains command-line parameters to execute a corresponding service.
- Each time a service description yml file changes (or a new one is placed in the folder),
helen should restart corresponding service using the information specified in the .yml file.
PROJECTS: helen
CHANGESET: create new component/module
DESCRIPTION:
An isolated task that does not require any knowledge of the project internals.
Currently, to set up the whole qua-kit environment, one has to run separately:
qua-server,helen, and allhelenservices (at leastsirenand one more computational service). This is not so convenient, so I propose to lethelenitself start the services she is aware of.The changed
helenpipeline as I imagine it:helenstarts as usual and from time to time executes a special function (maybe in a separate thread)bundledServicessubfolder w.r.t.helenexecutable.service-name.ymlfiles. Eachservice-name.ymlfile contains command-line parameters to execute a corresponding service.helenshould restart corresponding service using the information specified in the .yml file.