Configuration detection / specification

[sbruggmann]

In my test setup we have multiple Neos Settings.yaml

Configuration/Settings.yaml (no DB settings)
Configuration/Development/Settings.yaml (yes, has DB settings, but the local ones)
Configuration/Production/Settings.yaml (correct production DB settings)

synco-serve automatically took the ones from the Development/Settings.yaml, which is wrong.
After I deleted them, it took Settings.yaml, not Production/Settings.yaml

It would be nice to have a way to configure synco which environment it should take and optionally that it does merge the corresponding context and sub-context settings.

[skurfuerst]

@sbruggmann hey, the system simply calls ./flow configuration:show. I'll however add to the server side wizard that it prints the used context, and asks whether this is correct :)

As a workaround, you can try running "export FLOW_CONTEXT=...." and then run the server side command. Does this work for you?

All the best,
Sebastian

[sbruggmann]

@skurfuerst 🤦 I've tried FLOW_CONTEXT=Production curl .. instead of export FLOW_CONTEXT=Production; curl ...

But could still be interesting to have an option and config file server side.
To make it a no brainer.