Tell upaas operators to set the cache size limit (closes #251)
check / check (push) Waiting to run

"Running under upaas" listed PIXA_CACHE_MAX_BYTES as optional. Under
upaas the volume is a directory on the host's filesystem, so the
default, 75% of that filesystem's free space plus what the cache holds,
lets one pixa take three quarters of the space the host and every other
app have left. The section now says to set it and why. The default is
unchanged.

Model: opus-5-5
This commit is contained in:
2026-10-15 06:07:57 +00:00
parent 761ade2e36
commit 8f5abb0b3e
2 changed files with 11 additions and 2 deletions
+6
View File
@@ -30,6 +30,12 @@ P2: security: per-origin rate limiting
# Completed Steps
- 2026-10-15 "Running under upaas" in `README.md` tells the operator to set
`PIXA_CACHE_MAX_BYTES` (closes #251): it listed the variable as optional, but
under upaas the volume is a directory on the host's filesystem, so the
default, 75% of that filesystem's free space plus what the cache holds, let
one pixa take three quarters of the space the host and every other app had
left. The section now says so. The default is unchanged.
- 2026-10-15 the example config allowlists no host (closes #249): it allowlisted
`github.com` and `user-images.githubusercontent.com`, where anyone can put an
image, so a deployment set up as Getting Started says served those images to