-
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
docs: update installation guide #11160
Conversation
Signed-off-by: nitishfy <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix for CI linting error
Signed-off-by: nitishfy <[email protected]>
Signed-off-by: nitishfy <[email protected]>
The linter issues have been fixed now |
Co-authored-by: Traky Deng <[email protected]>
Then, you can run the following command to clone the APISIX source code from Github: | ||
|
||
```shell | ||
git clone --depth 1 --branch ${APISIX_VERSION} https://github.com/apache/apisix.git apisix-${APISIX_VERSION} | ||
git clone --depth 1 --branch master https://github.com/apache/apisix.git |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes.
@@ -271,9 +271,13 @@ You can configure your APISIX deployment in two ways: | |||
apisix start -c <path to config file> | |||
``` | |||
|
|||
APISIX will use the configurations added in this configuration file and will fall back to the default configuration if anything is not configured. | |||
APISIX will use the configurations added in this configuration file and will fall back to the default configuration if anything is not configured. Generally, APISIX gets installed at `/usr/local/apisix/` directory, so your configuration file will be present at `/usr/local/apisix/conf/` path. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
APISIX will use the configurations added in this configuration file and will fall back to the default configuration if anything is not configured. Generally, APISIX gets installed at `/usr/local/apisix/` directory, so your configuration file will be present at `/usr/local/apisix/conf/` path. | |
APISIX will use the configurations added in this configuration file and will fall back to the default configuration if anything is not configured. Generally, APISIX gets installed at `/usr/local/apisix/` directory, so the configuration file will be present at `/usr/local/apisix/conf/`. |
APISIX will use the configurations added in this configuration file and will fall back to the default configuration if anything is not configured. | ||
APISIX will use the configurations added in this configuration file and will fall back to the default configuration if anything is not configured. Generally, APISIX gets installed at `/usr/local/apisix/` directory, so your configuration file will be present at `/usr/local/apisix/conf/` path. | ||
|
||
If you are unable to start APISIX and observe `Bind address already in use` in logs, it means the ports APISIX wants to use are already occupied by other running processes. Upon reviewing the use of these processes, you may decide to kill these processes or configure APISIX to use other non-conflicting ports. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is pretty basic stuff, we can remove this.
|
||
If you are unable to start APISIX and observe `Bind address already in use` in logs, it means the ports APISIX wants to use are already occupied by other running processes. Upon reviewing the use of these processes, you may decide to kill these processes or configure APISIX to use other non-conflicting ports. | ||
|
||
Other way is to configure the default listening port to other available port on your local machine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto
Do we need this PR still? The most beneficial change here as it seems is to re-arrange etcd and APISIX installation order. Let's re-align what needs to be done here and move this effort forward. Thanks. |
🏓 |
The only change beneficial here is to adjust the order of APISIX and etcd installation. This can be addressed in a separate PR. Closing this PR as it is stagnant. |
Description
Generally, when you're trying to install the apisix from the installation guide, sometimes you come across the
Address Bind already in use
error logs when trying to start the apisix server. This is likely caused due to the unavailability of the port. Mostly, it happens if you've installed the apisix using docker due to which the ports get equipped. Hence, when you try installing the apisix locally, you get the error logs.This PR mentions this minor information with solution to this problem. There is a little refactoring of the docs as well. Since, it is required to install the
etcd
first, the installation part of etcd is moved first, followed by installation ofapisix
server installation.Fixes # (issue)
Checklist