Skip to content

Configuration detection / specification #8

Open
@sbruggmann

Description

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.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions