How to build a complete, real-world application from scratch with Ruby on Rails step by step.
A lot of Ruby code is "magic". We'll explain the magic and see how it works using the powerful tools Ruby gives us.
Accept subscription and one-time payments with Stripe in your Rails apps
Expert advice on keeping Rails apps organized and fast.
Cheap, easy hosting for Ruby and Rails apps.
Launch your product business way faster with our SaaS template.
A weekly podcast on web development and building products with Ruby, Rails, Javascript, and more.
A few of the Open Source projects we do at GoRails.
Build a Ruby on Rails app in 48 hours with us.
Help Junior developers get hired by sharing small projects to build their resume with paid work.
Find your next Ruby on Rails Job.
So far, our project has been a single line of operation. We can refactor this to use methods to reuse code in various ways.
Loops allow you to run code multiple times. This is handy when you need to process a group of items one at a time until the entire group is finished. We'll also learn about Ruby blocks to define the set of operations.
Object oriented programming and Ruby go hand in hand. This lesson, we'll learn how to define classes and create instances of them to organize our code.
We're going to build a Blog with Ruby on Rails so let's start by making sure we have everything installed and create our new Rails app
Now that we've created a new Rails app, let's take a look at the files generated and learn what they do
The first thing we need is a database table to store our blog posts. We create a Rails model (the M in MVC) to create the database and a Ruby class for us to interact with the database table.
An index page allows us to display all the blog posts in our database. We will learn how to setup routes that point to controllers and actions that render HTML.
We need a way to view individual Blog Posts on their own URLs now. That's where our Show action comes into play and we will learn how to build that in this lesson.
We now want to create new Blog Posts in our Rails app, not directly in the database. To do this, we're going to start by building a new action and form for inputting data for our Rails model.
Handling form submissions with Rails teaches us about strong parameters and saving data with our Rails models into the database.
Implementing Edit and Update actions are straightforward now. We can reuse what we've learned with New and Create and reuse some of the logic to edit and update database records in Rails.
We want to be able to delete blog posts we no longer want. We'll learn how to delete blog posts and refactor our code in this lesson.
Anyone can create, edit, or delete a blog post in our Rails app currently. In this lesson, we'll add authentication so only allowed users can do those actions.
Our blog doesn't look great. We're going to install TailwindCSS so we can easily style our Rails application however we want.
Next we're going to deploy our Rails blog application to production! This is a huge step, but also
Scheduling blog posts to be published in the future is the next feature we're going to add. In this lesson, we'll talk about several options we have to implement this and then choose one to build.
Our scheduled blog posts adds some complexity to our app. In this lesson, we're going to write some tests to make sure that our code does what we want it to do.
Scopes are a way for us to change the way a database table is queried. For example, we can use them to change the ordering of the results so certain records are first.
ActionText is a feature of Rails that allows you to add rich text including file uploads to any of your models. This is a perfect fit for our Blog Posts, so we're going to replace the text column with a rich text field with ActionText.
ActionText builds on top of the ActiveStorage file uploads feature in Rails, so we're going to configure Amazon S3 storage so we can upload files in production
Join 87,563+ developers who get early access to new tutorials, screencasts, articles, and more.
We care about the protection of your data. Read our Privacy Policy.
