When following the user guide, we get some examples like:
topology /dump = "./my_topology_dump"
which actually writes into Orchestrator/bin, regardless of the current-working directory when
you ran ./orchestrate.sh. For most users the orchestrator bin directory is not going to be writeable
(I'm assuming a system-wide Orchestrator is the aim), or is at least a poor default as they are working
in their own application. I'd suggest that this should default to the current working directory on startup.
This is the same argument as suggested in my comments on #192 . It's difficult to see why any
of the default directories should be "Orchestrator" or "Orchestrator/bin", maybe with the exception
of the path /engine directory.
There is the configuration file Config/Orchestrator.cfg in the 1.0.0-alpha version, but by default
this is also setting things like Output relative to the orchestrator binary (AFAICT).
When following the user guide, we get some examples like:
which actually writes into
Orchestrator/bin, regardless of the current-working directory when you ran./orchestrate.sh. For most users the orchestrator bin directory is not going to be writeable (I'm assuming a system-wide Orchestrator is the aim), or is at least a poor default as they are working in their own application. I'd suggest that this should default to the current working directory on startup.This is the same argument as suggested in my comments on #192 . It's difficult to see why any of the default directories should be "Orchestrator" or "Orchestrator/bin", maybe with the exception of the
path /enginedirectory.There is the configuration file
Config/Orchestrator.cfgin the 1.0.0-alpha version, but by default this is also setting things likeOutputrelative to the orchestrator binary (AFAICT).