SPEC follows milestones 1 and 2: build order, two size limits, GeoJS answers in memory #35

Merged

clawbot merged 1 commits from issue-16-milestones into next

2026-09-29 02:10:35 +02:00

Author	SHA1	Message	Date
sneak	5971529abb	SPEC follows milestones 1 and 2: build order, two size limits, GeoJS answers in memory (closes #16 ) The build order starts with milestone 1 and milestone 2, then keeps the earlier stages in their order, less what the two milestones build. Milestone 2 builds the container image with runit and the health check, so it answers /_smallwebwaf/healthz before the other admin endpoints. The four body-size settings become SWWAF_REQUEST_MAX_BYTES and SWWAF_RESPONSE_MAX_BYTES, since bodies pass through unchanged; the four timeouts stay. GeoJS answers are kept in memory; lookups.json comes in milestone 3 or later, as sneak ruled. README.md: the two sentences this change made wrong. Model: opus-5-5	2026-09-29 00:00:20 +00:00

Author

SHA1

Message

Date

sneak

5971529abb

SPEC follows milestones 1 and 2: build order, two size limits, GeoJS answers in memory (closes #16 )

The build order starts with milestone 1 and milestone 2, then keeps the
earlier stages in their order, less what the two milestones build.
Milestone 2 builds the container image with runit and the health check,
so it answers /_smallwebwaf/healthz before the other admin endpoints.

The four body-size settings become SWWAF_REQUEST_MAX_BYTES and
SWWAF_RESPONSE_MAX_BYTES, since bodies pass through unchanged; the four
timeouts stay.

GeoJS answers are kept in memory; lookups.json comes in milestone 3 or
later, as sneak ruled.

README.md: the two sentences this change made wrong.

Model: opus-5-5

2026-09-29 00:00:20 +00:00