In this final part of our Rails API app series we’ll talk about specs, code coverage, continuous integration and deployment - and how to be certain your application is working.continue reading »
Time to deal with authenticating users in our bookstore application.continue reading »
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.continue reading »
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?continue reading »
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.continue reading »
I’ve been rather busy lately, and my progress in learning Vue.js has slowed down. However, I think that I’m ready to dive into making something more resembling a real application than Monster Hunter and GalaxyQuest. I believe that you learn best when your objective is teaching it to somebody else. Therefore, over the next couple of weeks I’ll be making and refining a simple bookstore app1, using Rails 5.1 for the API backend, and vue.continue reading »