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

Override config file arguments from CLI #176

Closed
ghenadiibatalski opened this issue Jul 28, 2022 · 2 comments · May be fixed by AKJUS/node#18, Zionsammy/node#4 or nerdy-tech-com-gitub/node#5
Closed

Override config file arguments from CLI #176

ghenadiibatalski opened this issue Jul 28, 2022 · 2 comments · May be fixed by AKJUS/node#18, Zionsammy/node#4 or nerdy-tech-com-gitub/node#5
Labels

Comments

@ghenadiibatalski
Copy link

Hello and thank you for this wonderful product! I'm facing a problem, that i need to override at least the --directory from a command line even if this is already configured via the config file. Could you please make a CLI arguments a higher precedence over the config file?

Thanks and kind regards, Gena

@75lb
Copy link
Member

75lb commented Jul 31, 2022

Hi, yes this looks like a bug.. if you set the --config flag you can inspect the config that ws is using, e.g.

$ ws --port 8030 --config
{
  port: 8030,
  stack: MiddlewareStack(3) [ LwsAuth, Static ],
  view: CliView {}
}

Do you find that the --config output is correct but is not being respected? I imagine this is a quick fix, will look into it..

@75lb
Copy link
Member

75lb commented Aug 1, 2024

Fixed and released in local-web-server v5.4.0

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