v1.10.0

What's Changed

v1.10.0 focuses on the database and brings two major changes:

• Rage's own Connection Pool is now enabled by default. We've implemented lots of improvements and stability fixes to it while preserving excellent performance. Active Record versions starting with 6.0 are supported.
• You can now use the -d option with the rage new command to preconfigure the app for the selected database. Thanks to standalone_migrations, commands like rage db:migrate or rage db:seed are supported out-of-the-box.

Other changes in the release:

• Add rage middleware and rage version commands.
• Log to STDOUT by default in production.

Full Changelog: v1.9.0...v1.10.0

v1.9.0

What's Changed

• Allow to serve static files from the public directory in #100
• Add request methods to the Rage::Request class by @cuneyter in #97
• Correctly set Rails env in #102
• Rails 7.2 compatibility in #101

Full Changelog: v1.8.0...v1.9.0

v1.8.0

What's Changed

v1.8.0 adds support for WebSockets! Head out to the WebSockets page to see it in action. Make sure to check the benchmarks!

On the note of benchmarks, Rage is now part of the TechEmpower benchmark project! And we all look forward to seeing the official results 😬🤩

Full Changelog: v1.7.0...v1.8.0

v1.7.0

What's Changed

• Controller parameters wrapping feature by @alex-rogachev in #89
• Unknown Environment Error Handling by @cuneyter in #95
• Allow rescue_from handlers to not accept arguments in #93

New Contributors

• @cuneyter made their first contribution in #95

Full Changelog: v1.6.0...v1.7.0

v1.6.0

What's Changed

• Improve Rage.multi_application.
  • Rage now correctly handles internal Rails routes, e.g. /rails/action_mailbox/relay/inbound_emails.
• Support legacy root helpers.
  • Rage now supports legacy root helpers, e.g. get "/photos/:id" => "photos#show" or get "search" => :index.

Full Changelog: v1.5.1...v1.6.0

v1.0.0

The first production-ready release of Rage is out! 🎉

We have implemented a lot of exciting features, and there is still more to come! Thank you to all the contributors and folks who provided extremely valuable feedback! Unfortunately, I can’t thank my wife as she beats me with her little fists every time I try to work on this project. But, hopefully, we will figure it out before v2 is out.