Skip to content

Support for default configuration outside of phar #16

@EHLOVader

Description

@EHLOVader

Does this offer support for a default config.json in a templates folder or similar outside of the phar but relative to the current working directory?

Could it? It would save from having to type the path in every command without having to aliasing it or recompiling this from a fork.

Metadata

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