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 # custom CSS 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…

Conserving unicorns by serving images with nginx?

개발

Falco (Falco) 1월 30, 2021, 3:16오후 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.

글		댓글	조회수
Enable a CDN for your Discourse Self-Hosting cdn , configuring , how-to	72	295020	10월 4, 2025
Update Avatar Image Serving - Remove Proxy Method Feature	4	234	2월 6, 2025
Best configurations for speeding up standalone discourse Self-hosting server-resources	25	4432	2월 14, 2024
Avatar Proxy and CDN Hot-Link Protection Support	6	349	2월 5, 2025
Using multiple containers - what needs to be shared? Self-hosting	1	966	3월 3, 2021

Conserving unicorns by serving images with nginx?

Related topics