The discussion revolves around whether it makes sense to use an external Nginx server to serve static files for Discourse. valsha asks about configuring Nginx to handle static assets like /assets, /user_avatar, and /uploads with caching headers, noting they are using Nginx outside the container and referencing the official Discourse installation guide. pfaffman questions the need for this setup, suggesting it’s unnecessary, hard to maintain, and offers little benefit, especially since a reverse proxy is already in use. valsha clarifies that the external Nginx is needed because other sites run on the same server, making direct serving of Discourse static files a practical necessity.
I don’t think that there is any reaon to have the external NGINX serve those files directly. I think that you can, but it’ll be hard to configure, hard to maintain, and provide virtually no benefit. If you thought that it would make things faster, why would you use a reverse proxy at all?