Question 1

How to add session support to a ningle app?

Accepted Answer

ningle doesn't include sessions in its core. Use Lack.Middleware.Session with Clack's builder function, as shown in the README: wrap your app with (builder :session *app*) to enable sessions.

Question 2

ningle or Caveman: which is better for a new Common Lisp web project?

Accepted Answer

Choose ningle if you want minimal overhead and control without a project skeleton; opt for Caveman if you prefer a more structured, batteries-included approach with generated templates and conventions.

Question 3

Can ningle handle JSON APIs effectively?

Accepted Answer

Yes, its low-level request/response access allows manual JSON parsing and setting appropriate headers, but you'll need to handle serialization and validation yourself or with external libraries.

Question 4

How to deploy a ningle application in production?

Accepted Answer

Deployment relies on the underlying Clack server (e.g., Hunchentoot). Configure Clack settings for performance and use process managers like systemd, but ningle itself offers no built-in deployment tools.

Question 5

What are common middleware used with ningle?

Accepted Answer

Popular Lack middlewares include sessions, static file serving, and logging. Integrate them via Clack's builder, but note that ningle's minimalist design means you must research and add each middleware separately.

Question 6

Is ningle suitable for large-scale applications?

Accepted Answer

Its minimalism can be a benefit for microservices or APIs, but for large monoliths, the lack of built-in features may lead to fragmented codebases without additional structuring or libraries.

ningle

Overview

Use Cases

Not Ideal For

Pros & Cons

Pros

Related Projects

Found a gem we're missing?

Cons

Frequently Asked Questions