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

Have Command Line options override the config options? #796

Closed
peteruithoven opened this issue Aug 28, 2015 · 2 comments
Closed

Have Command Line options override the config options? #796

peteruithoven opened this issue Aug 28, 2015 · 2 comments

Comments

@peteruithoven
Copy link

There are cases where you'll want to put some general configuration into a config file but you want to change the startPath for example. For example to fix file watching on Linux (paulmillr/chokidar#343) I have to enable the usePolling (this can only be done through a config file). Then I have a Makefile with a start and test command in which I want to reuse the same configuration but I want to alter the startPath. It would be great if I could simply do the following:

start:
    ./node_modules/.bin/browser-sync start --config bs-config.js
test:
    ./node_modules/.bin/browser-sync start --config bs-config.js --startPath test.html

Currently the config overrule the commandline options, which seem counter intuitive in general?

@shakyShane
Copy link
Contributor

agreed

@shakyShane
Copy link
Contributor

this was added in 2.12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants