Question 1

Is Woo production ready?

Accepted Answer

Woo is still in beta, as warned in the README, so it might not be stable enough for critical production environments. It's best for development or non-critical use until a stable release.

Question 2

How to set up SSL with Woo?

Accepted Answer

Use the :ssl-cert-file and :ssl-key-file parameters in woo:run or clack:clackup, with optional passwords. SSL can be disabled by adding :woo-no-ssl to cl:*features* before loading.

Question 3

Woo vs Hunchentoot, which is better for Common Lisp?

Accepted Answer

Woo is optimized for high performance with libev and non-blocking I/O, ideal for low-latency APIs. Hunchentoot is more mature and stable, better for general-purpose web apps where stability is key.

Question 4

How to deploy Woo with Docker?

Accepted Answer

Woo provides Docker examples, like the Quickdocs API server Dockerfile. Containerize it by including dependencies like libev in the image, but ensure debug mode is off for production.

Question 5

Can Woo run on Windows?

Accepted Answer

No, Woo requires UNIX systems (GNU Linux, Mac, *BSD) and SBCL, so it's incompatible with Windows or other non-UNIX platforms.

Question 6

How to handle errors in Woo?

Accepted Answer

By default, debug mode is on, so the server may crash on errors. Set :debug nil in production to disable the debugger and implement custom error handling in your app.

woo

What is woo?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions