-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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: support multiple ports like stream listen in http and https listen port. #1195
Comments
Very good advice |
@wwd5613 welcome PR |
@wwd5613 can u show some example? |
that means: you want apisix can support multiple ports to start. now apisix just can start up on one port by the config parameter "node_listen ". just for the configuration in nginx |
I want to solve this issues. This is my first time to participate in apisix. |
@tzssangglass no problem. I have assigned this issue to you. If you have any questions, please feel free to talk to me. |
ok |
now i modified config.yaml as follows
and modified the ngx_tpl related places, as follows
in this way config.yaml can be parsed as the following configuration in nginx.conf
now my question is
|
support multiple listening ports, there are three styles:
apisix:
node_listen:
- 9080
- 9081
- 9082
apisix:
node_listen: 9080 9081 9082
apisix:
node_listen: 9080, 9081, 9082 Which is the one you would like? |
I vote to
|
Apache APISIX is now using style 1, I think it should be consistent, this is also a more common way in yaml |
In master branch, apisix/conf/config-default.yaml Lines 22 to 23 in b8e4b85
but apisix/conf/config-default.yaml Lines 88 to 90 in b8e4b85
so without considering backward compatibility, the question now is whether to consider backward compatibility, i cannot make a decision on my own. |
Or take a more complicated method, compatible with the original configuration method. If you need to support multiple ports like stream listen in http and https listen port,modify config.yaml like style 1. |
APISIX is using style 2 or 3 (only one port) currently. |
I think the compatibility design is reasonable, I plan to do this. |
No description provided.
The text was updated successfully, but these errors were encountered: