We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Type: Bug Report
Type checking and strict objects forbids my ability to start Flood on a unix socket on existing code
I should be able to set the port value to a String to start a listen server on a unix socket by passing a string into a server.listen() param via expressjs
Flood fails to start, demanding a port to be a number value
Adjust the config type checking to allow strings in the port value, and the host value to be optional.
--port
I would like to remove the need to run Flood on a unix domain socket behind an nginx reverse proxy, reducing the overhead that is involved with TCP
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Type: Bug Report
Your Environment
Summary
Type checking and strict objects forbids my ability to start Flood on a unix socket on existing code
Expected Behavior
I should be able to set the port value to a String to start a listen server on a unix socket by passing a string into a server.listen() param via expressjs
Current Behavior
Flood fails to start, demanding a port to be a number value
Possible Solution
Adjust the config type checking to allow strings in the port value, and the host value to be optional.
Steps to Reproduce
--port
Context
I would like to remove the need to run Flood on a unix domain socket behind an nginx reverse proxy, reducing the overhead that is involved with TCP
The text was updated successfully, but these errors were encountered: