If you’re new to the series, click here for part 1, part 2 and part 3. We now have a basic API where we can do basic queries for posts, comments and users, but speaking of users, we have no actual way of signing up or logging in or out. Let’s take care of that.
If you’re new to the series, click here for part 1 and part 2. So far we’ve taken care of our database schema, but we haven’t done much elsewhere so our api doesn’t really do anything yet. Let’s change that. Today we’re going to start work on adding the routes that will be the endpoints of our API.
In the last post, we set up our user model. Let’s add two more models and explore its relationship to the user model.
While Rails is a perfectly viable solution to spin out a quick API server, I must confess that one of the things about programming that I like the most is the constant learning. So recently I decided to build an API using tools I normally don’t use and documented the process so you can learn too.
For today’s excercise, we’re going to build a ROT13 translator. The name stands for ROTate 13, which means every character of a string will be shifted 13 characters ahead. For example, a becomes n, b becomes o, c becomes p and so on.
