Question 1

How does Hanami compare to Ruby on Rails?

Accepted Answer

Hanami offers a more modular and less opinionated architecture than Rails, focusing on maintainability and flexibility with independent libraries. However, Rails has a larger ecosystem and more built-in features, making it better for rapid prototyping. Hanami is ideal for teams prioritizing clean code separation over convention-over-configuration.

Question 2

How to handle authentication in Hanami?

Accepted Answer

Hanami doesn't include built-in authentication, so you need to integrate third-party gems like Warden or implement it manually using Hanami::Controller actions. This involves managing sessions or tokens, similar to other frameworks but within Hanami's structured approach, which can require more initial setup.

Question 3

Is Hanami good for building RESTful APIs?

Accepted Answer

Yes, Hanami is well-suited for APIs due to its modular components like Router and Controller, which provide clean routing and action handling. You can use JSON serialization with Hanami::View or skip views for API-only responses, making it flexible for backend services.

Question 4

Can I use Hanami with a frontend framework like React?

Accepted Answer

Absolutely, Hanami handles the backend, and you can serve static assets via Hanami::Assets or expose API endpoints. Integrate React by managing frontend resources through the asset pipeline or using separate builds, though this may require additional configuration compared to full-stack JavaScript frameworks.

Question 5

What database adapters does Hanami support?

Accepted Answer

Hanami::DB supports multiple SQL adapters like PostgreSQL, MySQL, and SQLite through its underlying library, as mentioned in the documentation. Check the Hanami::DB guides for specific setup details, but note that NoSQL or less common databases might require custom integrations.

Question 6

How to deploy a Hanami application?

Accepted Answer

Deploy Hanami apps like any Rack application using servers like Puma or Passenger, with environment-based configuration. Ensure to run database migrations during deployment and set up asset precompilation if using Hanami::Assets, similar to Rails but with Hanami's modular setup.

Hanami

What is Hanami?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions