Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: support multiple configuration files #40

Open
rsek opened this issue Oct 10, 2023 · 0 comments
Open

Feature Request: support multiple configuration files #40

rsek opened this issue Oct 10, 2023 · 0 comments

Comments

@rsek
Copy link

rsek commented Oct 10, 2023

Hi there. I use the CLI to work on multiple packages. Editing this file every time I switch packages is error-prone. I'd like it if there was a way to load a specific configuration file instead.

The most basic version of that might be an option that's appended to any command, e.g.: fvtt launch --config ./my/config/path/my-package.fvttrc.yml. It'd be convenient if there was a way to create a new config file in a specific location, too.

The ideal version

I'd love some kind of local config autodetection, paralleling other common Node developer dependencies. That way, I can just add ./fvttrc.yml to each package's .gitignore, rather than having to remember (always a gamble for me, TBH) to switch configurations each time.

Example

Say the CLI is installed to my_project/node_modules.

  1. if the CLI is invoked with a specific --config, it uses the specified path
  2. if no config was specified, it then checks for a local configuration at my_project/.fvttrc.yml
  3. if no local config is available, it falls back to its current behavior and uses the global configuration (if available).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant