Ahoy VS Devise

A full-featured, mountable analytics dashboard for your Rails app, which is a blatant rip-off of heavily inspired by Plausible Analytics, powered by Ahoy. Open source, though lots of changing parts: https://github.com/joshmn/ahoy_captain

For logging which functions were used you can use ahoy

Ahoy may be worth a try https://github.com/ankane/ahoy

I've slowly started ripping Google Analytics out of my Rails projects and replacing it with https://github.com/ankane/ahoy.

It's so much better! I can just use SQL to see what's going in and not get overwhelmed with 100's of visualizations and complicated dashboards.

it's just a database table, so yeah, a migration is fine: https://github.com/ankane/ahoy/issues/461

I'm using the ahoy gem for analytics on my website (https://github.com/ankane/ahoy).

I did server-side tracking test in a rails app, where I implemented a tracking gem called ahoy and blazer for visualization. It is very easy to set up, but a bit hard to use. Blazer can do a very basic visualization of the data if you know your SQL queries.

https://github.com/ankane/ahoy The ahoy gem is pretty useful for this. Data model is pretty simple, it will track unique user sessions and metrics you specify will be associated with these sessions. The gem also parses the user agent, so it will indicate whether a session was on mobile, desktop or tablet.

Since Rails 7, there's more and more tooling that enables us, developers, to roll our own authentication. Devise is great and has been an amazing companion over the years. It also has this neat little feature - an authenticated route constraint which "hides" certain routes from people that are not signed in.

[changelog] https://github.com/heartcombo/devise/blob/main/CHANGELOG.md [upgrade guide] https://github.com/heartcombo/devise/wiki/How-To:-Upgrade-to-Devise-4.9.0-%5BHotwire-Turbo-integration%5D

As much as this article is about user authorization, there's something important we need to cover: user authentication. Without it, any authorization policies we try to define later on will be useless. But there is no need to write authentication from scratch. Let's use Devise.

With around 50 new gems released daily, it is common to use trending libraries for managing everyday tasks. You probably use Devise for authentication, Cancan for authorization, Kaminari for pagination, or run tests with Rspec.

Devise is an authentication library built on top of Warden, a Rack-based authentication framework.

devise: An authentication library designed for Rails

I used Devise, this is a Ruby on Rails app

In this article, we will explore how to implement authentication in a Rails 7 application using the popular devise gem. Authentication is a crucial aspect of web development, allowing users to securely access and interact with your application. By following this step-by-step guide, you will learn how to set up devise, configure authentication routes, create user models, and enhance your application with authentication features.