Wisp

Specific best practices and architectural patterns when working with Wisp.

Language / Topic

Gleam

Rules

Wisp · balanced balanced

- Manage HTTP requests natively processing the `wisp.Request` and `wisp.Response` structures inside pure functions.

- Implement concurrency safely relying consistently entirely on the Erlang/OTP actor model natively underlying Gleam.

- Configure explicit routing natively using Gleam's `case` pattern matching on request path segments.

- Read environment settings cleanly fetching variables through `gleam/erlang/os` instead of hardcoding host values.