Time to deal with authenticating users in our bookstore application.
We have two more things to tackle before our Rails API app is an MVP: namespacing the controllers and creating an authentication mechanism. We’ll tackle namespacing the controllers in this article - it might seem wordy, but it’s for a good reason.
Oh yeah. Now we’re going hardcore. Well, not really.
While Rails embraces a continuously changing data model, it’s always good to stop and think for a minute about the domain we’re trying to magically lockwithin an app. We’re building a bookstore. So what’s in one?
It’s time to continue with our foray into Rails API app with Vue.js frontend! In Part 0 we discussed what technology we’ll be using and why - I highly recommend you read through it if you haven’t already. Now it’s time to get our Rails on.
Okay, Thursday project. It’s my day off this week, what can I do.
I’m still on this Vue.js kick, so while studying Components, I built myself a little app.
I’m studying Vue.js right now - here’s a simple app that I made in the process.