I’ve been thinking of trying to conserve memory-heavy unicorn instances by configuring my external nginx (which I already have for serving 502 maintenance page and for correctly attributing IPv6 addresses) to also serve requests for images; with the intent of getting much of the value of moving them…

We already serve the images using the internal nginx in the container. config/nginx.sample.conf main location ~ /stylesheet-cache/ { add_header Access-Control-Allow-Origin *; try_files $uri =404; } …

Oh. At least now the next person with this bright idea might find it when they search for it. Many thanks! :grin:

I would guess that enabling caching on the external nginx would have the same benefit with respect to loading the unicorns, without having to set up a CDN. I see cache control headers on all the javascript assets, so I might give this a try… … well, I see the internal nginx is also already using pr…

Conservando unicórnios servindo imagens com nginx?

Dev

Falco (Falco) Janeiro 30, 2021, 3:16pm 4

If you want to help your unicorns, one thing that actually helps is Enable a CDN for your Discourse, as it will cache the few assets that are served on unicorns like the stylesheets.

2 curtidas

Tópico		Respostas	Visualizações
Enable a CDN for your Discourse Self-Hosting cdn , configuring , how-to	72	294017	4 de Outubro de 2025
Update Avatar Image Serving - Remove Proxy Method Feature	4	119	6 de Fevereiro de 2025
Best configurations for speeding up standalone discourse Self-hosting server-resources	26	4172	14 de Fevereiro de 2024
Avatar Proxy and CDN Hot-Link Protection Support	6	214	5 de Fevereiro de 2025
Using multiple containers - what needs to be shared? Self-hosting	2	908	3 de Março de 2021

Conservando unicórnios servindo imagens com nginx?

Tópicos relacionados