After an initial install via , hanami offers two commands:

Generates a Hanami application with the given APP name, in a new directory from the current location.

  1. $ hanami new bookshelf # generates a new Bookshelf application in ./bookshelf
  2. $ hanami new my_app # generates a new MyApp application in ./my_app

hanami version

Displays the Hanami version of the currently installed gem.

  1. $ hanami version
  2. v2.0.0

Project commands

When executed from within a hanami project, hanami offers a different set of commands.

These commands can be listed using the --help flag.

  1. $ bundle exec hanami --help
  3. Commands:
  4.   hanami console                              # Start app console (REPL)
  5.   hanami generate [SUBCOMMAND]
  6.   hanami middleware                           # Print app Rack middleware stack
  7.   hanami routes                               # Print app routes
  8.   hanami server                               # Start Hanami app server
  9.   hanami version                              # Print Hanami app version
  2. bookshelf[development]>

This command accepts an engine argument that can start the console using IRB or Pry.

hanami generate

Hanami 2.0 provides two generators, one for actions and one for slices.

  1. $ bundle exec hanami generate --help
  4.   hanami generate action NAME
  5.   hanami generate slice NAME

These can be invoked as follows:

  1. $ hanami generate action books.show
  2. $ hanami generate slice api

See the actions and guides for example usage.

Displays the Rack middleware stack as currently configured.

  1. $ bundle exec hanami middleware
  3. /    Dry::Monitor::Rack::Middleware (instance)
  4. /    Rack::Session::Cookie
  5. /    Hanami::Middleware::BodyParser
  1. $ bundle exec hanami middleware --with-arguments
  3. /    Dry::Monitor::Rack::Middleware (instance) args: []
  4. /    Rack::Session::Cookie args: [{:key=>"my_app.session", :secret=>"secret", :expire_after=>31536000}]
  5. /    Hanami::Middleware::BodyParser args: [:json]

hanami routes

Displays your application’s routes.

By default, routes are displayed in “human friendly” format. Routes can be inspected in csv format via the format option:

  1. $ bundle exec hanami routes --format=csv
  3. METHOD,PATH,TO,AS,CONSTRAINTS
  4. GET,/books,books.index,"",""
  6. POST,/books,books.create,"",""

Launches hanami’s development server for developing against your application locally.

  1. $ bundle exec hanami server
  3. 14:33:28 - INFO - Using Guardfile at bookshelf/Guardfile.
  4. 14:33:28 - INFO - Puma starting on port 2300 in development environment.
  5. 14:33:28 - INFO - Guard is now watching at 'bookshelf'
  6. [43884] Puma starting in cluster mode...
  7. [43884] * Puma version: 6.0.0 (ruby 3.1.0-p0) ("Sunflower")
  8. [43884] *  Min threads: 5
  9. [43884] *  Max threads: 5
  10. [43884] *  Environment: development
  11. [43884] *   Master PID: 43884
  12. [43884] *      Workers: 2
  13. [43884] *     Restarts: (✔) hot (✖) phased
  14. [43884] * Preloading application
  15. [43884] * Listening on http://0.0.0.0:2300
  16. [43884] Use Ctrl-C to stop

This server is for local development only. In production, use the following to start your application serving web requests with Puma:

  1. bundle exec puma -C config/puma.rb

hanami version

Prints the version of the installed hanami gem.

  1. $ bundle exec hanami version
  2. v2.0.0