CLI Config + global options

[swalkinshaw]

It would be nice to have a config system for trellis-cli itself. This means both a global config (likely in homedir) and local config overrides per project (in .trellis/config.yml). Right now there's probably only one global flag which is disabling virtualenv. However this feature would also allow us to build some more verbose logging output.

The ideal solution to global flags and config values would follow the standard precedence feature of CLIs:

1. explicit CLI flag
2. local config (if exists)
3. global config

[robrecord]

It would be nice to define the path to the trellis instance in this directory. Eg. If I am in the project root, the site is in /site and trellis is in /trellis, allow me to invoke trellis-cli without having to change directory.

[swalkinshaw]

have you tried this? It should work as you expect

…

On Mon, Oct 28, 2019, 3:18 PM Rob Record ***@***.***> wrote: It would be nice to define the path to the trellis instance in this directory. Eg. If I am in the project root, the site is in /site and trellis is in /trellis, allow me to invoke trellis-cli without having to change directory. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#70?email_source=notifications&email_token=AACIFNPL5IQC2M565W7R733QQ3YD3A5CNFSM4IZWB5X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECNA6CA#issuecomment-546967304>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACIFNLX3H4WPXN5QK6VATTQQ3YD3ANCNFSM4IZWB5XQ> .

[robrecord]

TLDR; Yes it does, you're right.

I did try, but something must have been wrong.
I tried with a fresh install and it worked. So I overhauled my trellis installation with fresh files, and of course, it worked.

Thanks!