This plan verifies a containerized Nivo website build with a co-located Storybook at /storybook/.
- Docker is running.
- You are in the repo root.
Bring up the website-only stack:
docker compose -f deploy/compose.website.yml up -d --buildSmoke checks:
curl -sS -I http://localhost:8080/ | tr -d '\r'
curl -sS -I http://localhost:8080/storybook/ | tr -d '\r'
curl -sS -I http://localhost:8080/storybook/sb-manager/runtime.js | tr -d '\r'Expect:
/returns200andCache-Control: public, max-age=1800/storybook/returns200- Storybook hashed assets return
Cache-Control: public, max-age=31536000, immutable
Bring it down:
docker compose -f deploy/compose.website.yml down --remove-orphansThe website includes /<chart>/api/ pages that POST chart props to a render API.
This repo historically used https://nivo-api.herokuapp.com/nivo for that, but if you want those pages to work without relying on an external service, the render API needs to be self-hosted and proxied under the same origin (e.g. at /nivo/).