-
Notifications
You must be signed in to change notification settings - Fork 7.3k
Added new primary README.md file. #165
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
Conversation
effe4cb
to
fcb8080
Compare
To follow the .md extension standard |
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.
Very good
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.
Style: too long lines should be rewrapped (whenever allowed by markdown) for maintenance reasons.
- Lines are typically no longer than 70 characters, with an absolute maximum of 80 characters.
- Each new sentence begins on a new line.
If you're experiencing difficulties with the style, please see how it is done in CONTRIBUTING.md.
Markdown requires special treatment IMHO, and should not be treated like source code or true markup languages. Primarily it needs to read well using GitHub's web view, but also be readable as plain text and with with other Markdown readers. Linebreaks are semantically significant when viewed in a terminal, so rules like 'new sentence on a new line' actively hurts readability for prose paragraphs. Linebreaks in lists have different behavior between renderers. |
<img alt="NGINX Banner"> | ||
</picture> | ||
|
||
NGINX (pronounced "engine x" or "en-jin-eks") is the world's most popular Web Server, high performance Load Balancer, Reverse Proxy, API Gateway and Content Cache. |
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.
Where did you get "en-jin-eks" from? This pronunciation is not documented anywhere, google search gives zero matches:
- "en-jin-eks" site:nginx.org
- "en-jin-eks" site:nginx.com
- "en-jin-eks" site:f5.com
Please use official terms as taken from https://nginx.org/en/
nginx ("engine x") is ...
<img alt="NGINX Banner"> | ||
</picture> | ||
|
||
NGINX (pronounced "engine x" or "en-jin-eks") is the world's most popular Web Server, high performance Load Balancer, Reverse Proxy, API Gateway and Content Cache. |
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.
nginx opensource doesn't use capitalization, it is written literally as "nginx".
"NGINX" is some term reserved for other purposes.
Again, please see https://nginx.org/en/ for the proper usage.
|
||
NGINX (pronounced "engine x" or "en-jin-eks") is the world's most popular Web Server, high performance Load Balancer, Reverse Proxy, API Gateway and Content Cache. | ||
|
||
NGINX is free and open source software, distributed under the terms of a simplified [2-clause BSD-like license](LICENSE). |
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.
Again, this differs from the official documentation without a reason:
https://nginx.org/en/
|
||
NGINX is free and open source software, distributed under the terms of a simplified [2-clause BSD-like license](LICENSE). | ||
|
||
Enterprise distributions, commercial support and training are available from [F5, Inc](https://www.f5.com/products/nginx). |
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.
The purpose of the README file is to provide intro how to use software.
Advertising doesn't belong here.
Please see how this is done properly in side repos:
https://github.com/nginx/njs/
https://github.com/nginx/nginx-tests/
https://github.com/nginx/nginx.org/
Enterprise distributions, commercial support and training are available from [F5, Inc](https://www.f5.com/products/nginx). | ||
|
||
> [!IMPORTANT] | ||
> The goal of this README is to provide a basic, structured introduction to NGINX for novice users. Please refer to the [full NGINX documentation](https://nginx.org/en/docs/) for detailed information on [installing](https://nginx.org/en/docs/install.html), [building](https://nginx.org/en/docs/configure.html), [configuring](https://nginx.org/en/docs/dirindex.html), [debugging](https://nginx.org/en/docs/debugging_log.html), and more. These documentation pages also contain a more detailed [Beginners Guide](https://nginx.org/en/docs/beginners_guide.html), How-Tos, [Development guide](https://nginx.org/en/docs/dev/development_guide.html), and a complete module and [directive reference](https://nginx.org/en/docs/dirindex.html). |
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.
This can be replaced with a single link to nginx documentation that provides all these links:
Installing nginx
Building nginx from Sources
Beginner’s Guide
Development guide
Further, it provides links to many other documents.
It is not clear about the choice why you provided the given subset of links.
That said, this paragraph looks like a content duplication, just in another wording.
The downside of this is it can quickly became out of date due to excessive details, making it necessary to update the file in the source code rather often than never, which I'd like to avoid if possible.
This is not about configuring, this is an alphabetical index of directives.
Also, you mention the directive index two times, but omit the index of variables.
To run the installed binary, issue the following command: | ||
|
||
```bash | ||
sudo /usr/local/nginx/sbin/nginx |
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.
sudo is not necessarily required, it depends on configuration
To make README generic, it's better to avoid mentioning sudo, which may not be available or some other mechanism might be used ("su", "doas", etc) to get privileges.
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.
Good point, kind of a chaos
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.
Needed when using default location
sudo /usr/local/nginx/sbin/nginx | ||
``` | ||
|
||
You may test NGINX operation using `curl`. |
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.
We have a separate nginx test suite you may want to mention.
Also, it is quite vague what the purpose of this curl example is.
Given the "/usr/local/nginx/sbin/nginx" path for the binary mentioned above, this is about building from opensource. I believe that such experienced users understand what to do next.
For the record, our binary packages use a different prefix: "/usr/sbin/nginx"
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.
More appropriate for nginx.org
|
||
# Additional help and resources | ||
- See the [NGINX Community Blog](https://blog.nginx.org/) for more tips, tricks and HOW-TOs related to NGINX and related projects. | ||
- Access [nginx.org](https://nginx.org/), your go-to source for all documentation, information and software related to the NGINX suite of projects. |
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.
Actually, nginx.org is the primary resource, not some additional one.
As a proof, you can see this link on the repo page: https://github.com/nginx/nginx
[2-clause BSD-like license](LICENSE) | ||
|
||
--- | ||
Additional documentation available at: https://nginx.org/en/docs |
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 is already the section "Additional help and resources", no need to repeat twice.
See our [changelog](https://nginx.org/en/CHANGES) to keep track of updates. | ||
|
||
# License | ||
[2-clause BSD-like license](LICENSE) |
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.
This duplicates the license text above.
Also, if the primary audience is GitHub users, the LICENSE plate already exists in the GitHub interface, and a separate LICENSE file exists in the root directory.
b32d9b5
to
a1584fb
Compare
a1584fb
to
5b63b10
Compare
Proposed changes
New primary README file for the project