Nice work - quick, thorough, and to the point! I'm coming back to rails after a several year hiatus, and boy, has it changed (seems like for the better)! Thanks for sharing!!
Loved this video and I appreciate the tips about using the main branch and getting access to this feature I wonder if there is a good tailwind template or that woudl be a good idea for a new gem
I get "User must exist" when I submit a view from one of my controllers. How do I associate the User to the POST params so that it knows to save my model to my User? In devise this is current_user.
hey Ryan! assuming you have "Task" model first, your database "task" model should have "user_id". run this in the console: add_user_to_tasks user:references & rails db:migrate in TasksController: def create @post = Task.new(task_params) + @post.user_id = current_user.id end
I like to reuse the same conventions as the ones used in Devise. So usually I will have current_user and same for the methods so that I can reuse other gems without any charge (Authorization or Access control for example)
@@SupeRails Pundit is one. Also many examples for Rolify are based on the Devise conventions (unlike Pundit, I do not think that they are enforcing the conventions)
@@hiphopheadninethree if you are using Devise, use Devise confirmable (Episode 41): superails.com/posts/ruby-on-rails-41-devise-confirmable-no-more-users-with-fake-emails If you are using this (rails 8 authentication), try this: railsbytes.com/public/templates/Xg8sMD !! Curently I do not recommend using Rails 8 native authentication in production. It is 💩 comparing to Devise
🚨 The updated syntax is to use `bin/rails generate authentication`, not `bin/rails generate sessions`
Nice work - quick, thorough, and to the point! I'm coming back to rails after a several year hiatus, and boy, has it changed (seems like for the better)!
Thanks for sharing!!
Finally! Something that make more sense than fight with JS...
In what case are you fighting with JS on authentication?
@@SupeRails I mean make more sense, since everyone need auth. And JS keeps changing…
Great. Thanks for useful info.
テストするまでは今まで通り自前のログイン機能かdevice使い続けると思うけど新しい認証増えてるのは嬉しい😊
Loved this video and I appreciate the tips about using the main branch and getting access to this feature I wonder if there is a good tailwind template or that woudl be a good idea for a new gem
There's a place for that! github.com/rails/tailwindcss-rails/issues/382
please use following command for now.
"bin/rails generate authentication"
sessions has swapped with authentication
Right!!!
Glad I found this comment.. Thanks
To be clear, I do not recommend you to use this new Rails auth generator. Devise is way better!
Спасибо Ярослав за интересное и познавательное видео.
все для вас, дорогі друзі :)
@superails please revisit and expound on this built-in feature.
great video, do you think apart from basic authentication rails would implement oauth out of thee box?
I really really doubt that
I get "User must exist" when I submit a view from one of my controllers. How do I associate the User to the POST params so that it knows to save my model to my User? In devise this is current_user.
hey Ryan!
assuming you have "Task" model
first, your database "task" model should have "user_id".
run this in the console:
add_user_to_tasks user:references
&
rails db:migrate
in TasksController:
def create
@post = Task.new(task_params)
+ @post.user_id = current_user.id
end
@@SupeRails Thank you!
Why storing session in cookies is better than storing in session?
@@Helisltu this might explain www.rubanonrails.com/2/cookie-based-authentication-with-rails/20/secure-session#http-only-cookies
Is there any good reason to do this? Is the Devise gem dead or troublesome in some way?
No, I do not recommend to use this solution! Devise is perfectly good. I recommend Devise!
Hilarious thumbnail 😄
Great video 👍
Thanks bro. Although it's a bit misleading. Devise is very good, and it's going nowhere any time soon!
I like to reuse the same conventions as the ones used in Devise. So usually I will have current_user and same for the methods so that I can reuse other gems without any charge (Authorization or Access control for example)
I also like the devise naming. But.... I don't recall of any other gems that rely on having methods like "current_user"...?
@@SupeRails Pundit is one. Also many examples for Rolify are based on the Devise conventions (unlike Pundit, I do not think that they are enforcing the conventions)
So what you do for oauth?
@@tofuman9526 OAuth2 gem or doorkeeper.
Can you do video on how to handle email verification before allowing access to account
@@hiphopheadninethree if you are using Devise, use Devise confirmable (Episode 41):
superails.com/posts/ruby-on-rails-41-devise-confirmable-no-more-users-with-fake-emails
If you are using this (rails 8 authentication), try this: railsbytes.com/public/templates/Xg8sMD
!! Curently I do not recommend using Rails 8 native authentication in production. It is 💩 comparing to Devise
Great!
Finally!
I think we still need to wait a bit for this to be production-ready
What about OAuth implementation?
Check out episode #103 Simple Omniauth without Devise. That's what I use for superails.com/