Skip to content
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

Closed
meaz opened this issue Jul 12, 2018 · 5 comments
Closed

Advantage of files served by nginx directly #9

meaz opened this issue Jul 12, 2018 · 5 comments

Comments

@meaz
Copy link

meaz commented Jul 12, 2018

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

@ThomasLeister
Copy link
Owner

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.

@rugk
Copy link

rugk commented Jul 13, 2018

As said here one example may be:

And now (statically) gzip/brotli compress them and you've increased the performance really much. 😉

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.

@ThomasLeister
Copy link
Owner

I assumed @meaz s question would be about this systemd file parameter in particular, but apart from that @rugk is right, of course :-)

@rugk
Copy link

rugk commented Jul 13, 2018

Ah, indeed. I mostly read the issue title only.😁

@benediktg
Copy link
Contributor

@ThomasLeister Yes, this leads to files getting owned by the nginx group which ensures that nginx can deliver the files. 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants