-
Notifications
You must be signed in to change notification settings - Fork 18
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
Advantage of files served by nginx directly #9
Comments
I guess it makes files created by Prosody-Filer be owned by nginx group. Which would ensure that nginx can read the files. But maybe @benediktg (who committed this work) has some details. |
As said here one example may be:
In general the main reason is likely just performance. You avoid padding the request to prosody and thus just skip a few steps when answering the request. |
Ah, indeed. I mostly read the issue title only.😁 |
@ThomasLeister Yes, this leads to files getting owned by the nginx group which ensures that nginx can deliver the files. 😉 |
In the readme file, it is written:
# Group=nginx # if the files should get served by nginx directly:
What would be the advantages over letting the default setting to
Group=prosody-filer
The text was updated successfully, but these errors were encountered: