sdoc VS Devise

Once you feel comfortable with both Ruby and Rails, try building a few simple apps on your own by reading the Rails Guides and browsing the Rails API whenever you're stuck.

Hi. I'm a self-taught Ruby on Rails programmer. I have a question about the documentation at https://api.rubyonrails.org. On many of the pages, you'll see methods and their details. Below that, you'll often see examples using different options. This is where I have a question. An example might look like this:

If a method isn't documented in https://api.rubyonrails.org/ it shouldn't be used as we reserve the right to remove or change them at any point.

Rails still holds the top spot in getting things out the door in the shortest amount of time. So many example projects and tons of amazing libraries that are available. They absolutely have the best developer docs in the industry as far as I'm concerned.

https://guides.rubyonrails.org/

https://api.rubyonrails.org/

Phoenix/Liveview is a close second. I would personally use Phoenix/Liveview at this point because since I know that stack pretty well, but it is definitely not as easy as Rails to learn. However, once past the learning phase I think there's distinct advantages especially with Liveview.

Fly.io has a free hosting tier currently. You can also get some free servers through Oracle Cloud.

https://api.rubyonrails.org is your best friend. Check the docs before googling. Instant access to the source of functions. ApiDock is shit but continuously gets to the top of google search results.

For something more in-depth, besides the Rails Guides that have been mentioned already, you could also use the Rails API docs as a reference.

Yeah visit guides.rubyonrails.org if you want to see how to do a particular thing like validations and stuff and use this website https://api.rubyonrails.org/ for seeing method definitions their options etc.. These two websites pretty much conver everything. I specially use the second on pretty frequently. Also I think sublime text is better for ruby on rails than vs code but thats personal preference. The ruby doc website is pretty good to for documentation on rubies standard classes. Like if you are looking for some method to do something for a string you can just search string ruby and this comes up first, it contains all public methods for these classes and is pretty useful.

If you mean the Rails API Documentation, I mainly use it when I use a method I'm not familiar with (eg trying to adapt a StackOverflow suggestion).

However for smaller apps it might be an overkill. In "real-life" production systems, overengineering is one of the biggest crimes. This is true any framework and technology, so in Rails you might want to use Rodauth since it is big and interesting and challenging, but then again, if you are building a simple greenfield MVP you do not have the time or need, for a big, complex solution. In those cases Rails developers usually go for Devise. It is one of the most known Rails gems, in multiple Rails surveys it was both number 1 in popularity, likability and "most frustrating" rankings.

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.