Question 1

How do I add authentication to a Trot app?

Accepted Answer

Trot doesn't include built-in authentication; you need to implement it with custom Plugs. For example, add a Plug before routing to validate tokens or sessions, as shown in the Plug.Builder example in the README.

Question 2

Trot vs Phoenix: which is better for APIs?

Accepted Answer

Trot is lighter and ideal for simple APIs or microservices where you want minimal overhead and full control over Plug. Phoenix is better for complex applications with built-in real-time features, Ecto integration, and a larger ecosystem.

Question 3

How to serve static files with Trot?

Accepted Answer

Use the `static/2` macro in your router, like `static "/css", "assets"` to serve files from the "assets" directory. This is built-in and requires no additional setup beyond the macro call.

Question 4

Does Trot support WebSockets?

Accepted Answer

No, Trot is focused on HTTP APIs and doesn't have built-in WebSocket support. You'd need to integrate Cowboy directly or use another library like Phoenix Channels for real-time features.

Question 5

Can I use Ecto with Trot?

Accepted Answer

Yes, but Trot doesn't integrate Ecto directly. Add Ecto as a dependency and use it in your handlers, but you'll need to manage connections and queries manually without framework helpers.

Question 6

How to handle errors or custom middleware in Trot?

Accepted Answer

Use the `plug/2` macro or configure Plugs in `:pre_routing` and `:post_routing` settings. For error handling, define custom routes or Plugs to catch and respond to errors, as Trot doesn't provide a default error handler beyond 404.

trot

What is trot?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions