I am getting this error, "An error has occurred, this and all later migrations canceled: SQLite3::SQLException: no such table: users". Not sure what to do? I think i followed an old video of yours in rails 6 where we built the authentication manually. But now I had the users table, so I couldn't migrate the devise database. So then I tried to delete the other data base: rails db:drop. and now I get the above error and can't find any stack overflow guides to help.
I have a question, does there need to be a relationship from the blog to the user for a user to edit their post, or can the ID created by Devise be added to the blog table to filter it? If there isn't a rule that ensures only I can edit my posts, anyone else could potentially edit them
chris pls increase the font size next time it is really hard to read and follow
Your videos are really helpful Chris! Thank you
As always, thank you very much.
Thanks a lot! Great content!
Hello coach, thank you very much for your dedication, can I ask you a question? Wouldn't it be safer to use JWT instead of using cookies?
Cookies are safer than JWT.
Would you recommend having a look first at the rails 6 course that you have? As I see you implemented manually your built auth not using devise
We recommend Devise for actual use and building auth from scratch at least once to understand how Devise works.
I am getting this error, "An error has occurred, this and all later migrations canceled:
SQLite3::SQLException: no such table: users". Not sure what to do?
I think i followed an old video of yours in rails 6 where we built the authentication manually. But now I had the users table, so I couldn't migrate the devise database. So then I tried to delete the other data base: rails db:drop. and now I get the above error and can't find any stack overflow guides to help.
Fantastic content, as always.
Do you have videos for alternatives to Devise?
why do you think you need alternatives to Devise, what devise couldn't provide?
I have a question, does there need to be a relationship from the blog to the user for a user to edit their post, or can the ID created by Devise be added to the blog table to filter it?
If there isn't a rule that ensures only I can edit my posts, anyone else could potentially edit them
Keep watching. 😜
masterpiece
I just don't understand how we are able to access user_signed_in? method so easily ?
There must be something calling that method right ?
Devise gem handles that for you. without devise you can't check if user signedin or not.
that's one of the devise gem power, for sure devise Is the best gem ever
Why does the logout button need to be a button? I tried making it a link but got an error [No route matches [GET] "/users/sign_out"]
Because it is a DELETE request and browsers use forms for that. Links only make GET requests.
@@GorailsTV ahh ok that makes sense. Thanks!!