-
Notifications
You must be signed in to change notification settings - Fork 112
clarify allowed upload directories #1020
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
base: main
Are you sure you want to change the base?
clarify allowed upload directories #1020
Conversation
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 see that you've removed /tmp and /var/cache/nginx from the table. Is this intentional? Do we no longer support writes to these directories?
If so, I'm concerned this might be a "breaking change".
{{</bootstrap-table>}} | ||
|
||
**Uploaded files can be placed in:** |
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.
If I read this quickly, I'd ask: "What about /tmp and /var/cache/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.
This docs says the same thing in four ways:
- big table
- bulleted list
- bulleted list with more words
- plaintext code block
I think that's a lot more confusing than what we had. If AI wrote this, please keep in mind the F5 AI policy, especially
Review outputs from approved AI Applications
How about we just stick to the table and delete the other three?
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 four methods that @ryepup noted leads to inconsistencies such as https://github.com/nginx/documentation/pull/1020/files#r2334077715 .
|
||
| Directory | Master Read | Master Write | Worker Read | Worker Write | Recommended Use | | ||
|-------------------|:-----------:|:------------:|:-----------:|:------------:|----------------------------------| | ||
| /etc/nginx/ | ✔️ | ✔️ | ❌ | ❌ | Certificates, keys | |
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 config files are recommend here
| Directory | Master Read | Master Write | Worker Read | Worker Write | Recommended Use | | ||
|-------------------|:-----------:|:------------:|:-----------:|:------------:|----------------------------------| | ||
| /etc/nginx/ | ✔️ | ✔️ | ❌ | ❌ | Certificates, keys | | ||
| /opt/ | ✔️ | ✔️ | ✔️ | ❌ | Application files | |
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.
what's an example "Application file"?
| /var/www/ | ✔️ | ✔️ | ✔️ | ❌ | Static files (e.g. index.html) | | ||
| /tmp/ | ✔️ | ✔️ | ✔️ | ✔️ | Temporary files | | ||
| /var/cache/nginx/ | ✔️ | ✔️ | ✔️ | ✔️ | Cache data | | ||
| /etc/app_protect/ | ✔️ | ✔️ | ✔️ | ❌ | App Protect policies, logs | |
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.
app protect logs don't live here
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 would they live? Based on standard Linux conventions, I'd assume some /var
subdirectory
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 it's configurable via NGINX config, but this is a table for where users can upload files on their deployment. Users aren't uploading logs.
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.
Users aren't uploading logs.
But they do need to reserve space for their logs on their systems.
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.
But they do need to reserve space for their logs on their systems.
Not on NGINXaaS, that is not part of the user's responsibility. NGINXaaS manages the OS / filesystem, the user just focused on their NGINX config.
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.
see comments
Proposed changes
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩