Summary
apps/docs/operations/environment-variables.md lists REDIS_URL under a "Future variables" section as currently not used. It is already used: apps/api-local/src/index.ts reads process.env.REDIS_URL and wires it into the @fastify/rate-limit plugin as its store.
Motivation
Anyone setting up a new environment and reading this doc would conclude REDIS_URL is optional/unused and skip configuring it, when in practice the API's rate limiting depends on it.
Proposed Solution
Move the REDIS_URL row out of "Future variables" into the main environment variable table, with a description matching its actual role (rate-limit store for apps/api-local).
Scope
| Field |
Value |
| Area |
Docs, API |
| Protocol affected |
None |
| Network |
N/A |
| Breaking change? |
No |
Alternatives Considered
None, this is a straightforward factual correction.
Acceptance Criteria
Additional Context
Verified against apps/api-local/src/index.ts (reads process.env.REDIS_URL, wires into @fastify/rate-limit).
Summary
apps/docs/operations/environment-variables.mdlistsREDIS_URLunder a "Future variables" section as currently not used. It is already used:apps/api-local/src/index.tsreadsprocess.env.REDIS_URLand wires it into the@fastify/rate-limitplugin as its store.Motivation
Anyone setting up a new environment and reading this doc would conclude
REDIS_URLis optional/unused and skip configuring it, when in practice the API's rate limiting depends on it.Proposed Solution
Move the
REDIS_URLrow out of "Future variables" into the main environment variable table, with a description matching its actual role (rate-limit store forapps/api-local).Scope
Alternatives Considered
None, this is a straightforward factual correction.
Acceptance Criteria
REDIS_URLappears in the main environment variable table, not the future/unused sectionAdditional Context
Verified against
apps/api-local/src/index.ts(readsprocess.env.REDIS_URL, wires into@fastify/rate-limit).