pixelfed doesn't use nginx caching or file streaming #21

Open
opened 1 year ago by th · 2 comments
th commented 1 year ago
Owner

looks like all files are hitting the pixelfed-app container rather than the top level nginx

looks like all files are hitting the pixelfed-app container rather than the top level nginx
th added the
enhancement
label 1 year ago
th commented 1 year ago
Poster
Owner

one complication: nginx:alpine uses uid 101 for www-data while every other container assumes it matches debian's 33. we can hack that into the nginx container but it feels like a bit of a mess

one complication: nginx:alpine uses uid 101 for `www-data` while every other container assumes it matches debian's 33. we can hack that into the nginx container but it feels like a bit of a mess
th commented 1 year ago
Poster
Owner

cache must use Accept encoding in the key since the same URI is used for both json and html

cache must use `Accept` encoding in the key since the same URI is used for both json and html
Sign in to join this conversation.
Loading…
There is no content yet.