Question 1

How do I handle POST requests in Axiom?

Accepted Answer

Define a handler for the <<"POST">> method in your handle/3 function and use axiom:params/1 to extract form data or JSON payloads, similar to GET requests but with method-specific logic for processing.

Question 2

Axiom vs Chicago Boss for Erlang web development?

Accepted Answer

Axiom is a lightweight, Sinatra-style framework ideal for simple APIs or apps, while Chicago Boss is a full-stack framework with more features like ORM and real-time capabilities. Choose Axiom for minimalism, Chicago Boss for comprehensive solutions.

Question 3

How to implement authentication in Axiom?

Accepted Answer

Use the built-in session management via axiom_session:set/3 and axiom_session:get/2 to store user data, and implement a before_filter/1 to check authentication tokens or cookies, as Axiom doesn't have built-in auth.

Question 4

Does Axiom support WebSockets?

Accepted Answer

No, Axiom focuses on HTTP and doesn't natively support WebSockets. For real-time features beyond HTTP streaming, you need to integrate Cowboy's WebSocket handlers separately or use another Erlang library.

Question 5

How to serve JSON responses in Axiom?

Accepted Answer

Return a tuple like {200, [{<<"Content-Type">>, <<"application/json">>}], Body} where Body is a JSON-encoded binary, using libraries like jsx or jiffy for encoding in your handler.

Question 6

What templating engine does Axiom use and how to customize it?

Accepted Answer

Axiom uses ErlyDTL for Django templates, compiled into modules during rebar compile. Customize by editing .dtl files in the templates directory and passing proplists of parameters in axiom:dtl/2 calls.

Axiom

What is Axiom?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions