Skip to content

Should we have an options object that allows precedence for command-line arguments? #1

@nelsonic

Description

@nelsonic

Should we allow command-line arguments or system/deployment environment variables to take precedence over values defined in env.json or vice-versa?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions