4 Commits

Include renames

Author	SHA1	Message	Date
clawbot	baf457d21e	Bound concurrent image processing and upstream fetches (closes #64) ... Nothing bounded total in-flight work, so a burst of cache misses across hosts could exhaust memory. Two settings now do: max_concurrent_processing (default the CPUs Go uses) and upstream_connections (default 64, beside the per-host limit). A request that finds either full waits up to 10 seconds, then gets 503; a slot is released on every path. No request holds source bytes while it waits: a cached source is read only after the processing slot is taken, and a fetched one only while it holds its upstream connection. libvips runs one worker thread per image with its operation cache off. Both waits count toward downstream_timeout, as the README says. Model: opus-5-5	2026-09-29 10:32:16 +02:00
clawbot	56217cbf4a	Add the four settings the README documented but pixa lacked (closes #61) ... README.md documented access_control_allow_origin, upstream_fetch_timeout, upstream_max_response_size and downstream_timeout, but pixa did not know them, so a config following the README aborted startup. Each is now a setting with its PIXA_ variable, defaulting to the value that was fixed in the code: *, 30s, 50 MiB and 60s. Durations are Go duration strings and must be positive; the size is whole bytes, at most 1 GiB. The origin is * or one http or https origin written exactly as a browser sends it; anything else aborts startup. downstream_timeout sets both the server's write timeout and the per-request timeout. The owner approved the edits to existing tests. Model: opus-5-5	2026-09-29 08:49:18 +02:00
clawbot	0f3700f7f5	Abort startup on an unknown PIXA_ environment variable (closes #133) ... A variable whose name starts with PIXA_ but is neither a setting's variable, from the list pairing each config key with its variable, nor PIXA_CONFIG_PATH now aborts startup naming it, as an unknown config key does. PIXA_PORT is named with a pointer to PORT. The check runs after the config file loads, so the variables the file's env section sets are checked too. README.md says so under Configuration. Model: opus-5-5	2026-09-28 16:12:57 +02:00
clawbot	0f5bd51b09	Every setting can be given as an environment variable (closes #128) ... Each config key can now be set by PIXA_ plus the key in upper case ("." written as "_"), and the port by PORT. A present variable, even an empty one, is read before the config file through the existing typed getters, so every existing check covers it; errors name the key and the variable, never the signing key or metrics password. A variable named in the file's env: section overrides both. An empty string for blocked_networks or trusted_proxies is now an empty list. The image no longer bakes in config.docker.yml or passes --config; its HEALTHCHECK probes ${PORT:-8080}. The config file is looked for under /etc/pixa rather than /etc/pixad. Also covers #99. Model: opus-5-5	2026-09-28 13:46:56 +02:00