Heroku deployment in Ruby on Rails

Introduction

Heroku deployment lets you put your Rails app online so anyone can use it. It makes sharing your work easy without needing your own server.

You want to share your Rails app with friends or users on the internet.

You need a simple way to host your app without managing servers.

You want to test your app in a real online environment.

You want to deploy updates quickly and easily.

You want to use a free or low-cost hosting option for small projects.

Syntax

Ruby on Rails

heroku create
git push heroku main
heroku run rails db:migrate
heroku open

heroku create makes a new app on Heroku and links it to your project.

git push heroku main sends your code to Heroku to deploy.

Examples

You can name your app to make it easier to find.

Ruby on Rails

heroku create my-rails-app
# creates an app named 'my-rails-app' on Heroku

This uploads your code so Heroku can run it.

Ruby on Rails

git push heroku main
# deploys your current main branch to Heroku

Apply your database updates after deployment.

Ruby on Rails

heroku run rails db:migrate
# runs database changes on Heroku server

Quickly check your live app after deployment.

Ruby on Rails

heroku open
# opens your deployed app in the browser

Sample Program

This sequence shows the basic steps to deploy a Rails app to Heroku. First, you prepare your code with git. Then you create the Heroku app, push your code, update the database, and finally open the app online.

Ruby on Rails

# 1. Initialize git and commit your Rails app
$ git init
$ git add .
$ git commit -m "Initial commit"

# 2. Create Heroku app
$ heroku create

# 3. Push code to Heroku
$ git push heroku main

# 4. Run database migrations
$ heroku run rails db:migrate

# 5. Open your app in browser
$ heroku open

Important Notes

Make sure your Rails app has a Gemfile and uses PostgreSQL, as Heroku supports it by default.

Check your config/database.yml to use environment variables for production database settings.

Use heroku logs --tail to see live logs if your app has issues after deployment.

Summary

Heroku deployment puts your Rails app online easily without managing servers.

Use git commands to push your code and run migrations on Heroku.

Open your app in a browser to see it live after deployment.

Practice

1. What is the main purpose of deploying a Rails app to Heroku?

easy

A. To put the app online without managing servers

B. To write Ruby code faster

C. To create a local database

D. To debug Rails code automatically

Solution

1. Step 1: Understand Heroku's role

   Heroku is a platform that hosts apps so they can be accessed online without you managing the servers.

2. Step 2: Compare options

   Options B, C, and D describe development or debugging tasks, not deployment.

3. Final Answer:

   To put the app online without managing servers -> Option A

4. Quick Check:

   Heroku deployment = online app hosting [OK]

Hint: Heroku hosts apps online, no server setup needed [OK]

Common Mistakes:

• Confusing deployment with coding or debugging
• Thinking Heroku manages local databases
• Assuming Heroku speeds up writing code

2. Which command is used to push your Rails app code to Heroku?

easy

A. heroku push

B. heroku deploy app

C. rails deploy

D. git push heroku main

Solution

1. Step 1: Identify the correct git command

   Heroku uses git to receive code. The correct command is 'git push heroku main' to push the main branch.

2. Step 2: Check other options

   Options A, C, and D are not valid commands for pushing code to Heroku.

3. Final Answer:

   git push heroku main -> Option D

4. Quick Check:

   Push code with git push heroku main [OK]

Hint: Use git push heroku main to deploy code [OK]

Common Mistakes:

• Using 'heroku push' which is invalid
• Trying 'rails deploy' which doesn't exist
• Confusing Heroku CLI commands

3. After pushing your Rails app to Heroku, which command runs database migrations on Heroku?

medium

A. heroku run rails db:migrate

B. rails db:migrate

C. git migrate heroku

D. heroku migrate db

Solution

1. Step 1: Understand migration on Heroku

   To run migrations on Heroku's remote server, you use 'heroku run rails db:migrate'.

2. Step 2: Check other commands

   'rails db:migrate' runs locally, 'git migrate heroku' and 'heroku migrate db' are invalid commands.

3. Final Answer:

   heroku run rails db:migrate -> Option A

4. Quick Check:

   Run migrations remotely with heroku run rails db:migrate [OK]

Hint: Run migrations remotely with heroku run rails db:migrate [OK]

Common Mistakes:

• Running migrations locally instead of on Heroku
• Using invalid git commands for migration
• Confusing command order

4. You pushed your Rails app to Heroku but see an error when opening the app URL. What is a common cause?

medium

A. You did not install Ruby locally

B. You used 'git push origin main' instead of 'git push heroku main'

C. You forgot to run database migrations on Heroku

D. You opened the wrong browser

Solution

1. Step 1: Identify common deployment errors

   Forgetting to run migrations on Heroku often causes errors because the database schema is not updated.

2. Step 2: Evaluate other options

   You used 'git push origin main' instead of 'git push heroku main' means code wasn't pushed to Heroku, but question says code was pushed. Options A and D are unrelated to deployment errors.

3. Final Answer:

   You forgot to run database migrations on Heroku -> Option C

4. Quick Check:

   Missing migrations cause app errors on Heroku [OK]

Hint: Run migrations after push to avoid errors [OK]

Common Mistakes:

• Ignoring migrations after deployment
• Confusing git push origin with heroku
• Blaming local environment for Heroku errors

5. You want to deploy a Rails app with environment variables for API keys on Heroku. Which is the correct way to set them before deployment?

hard

A. Add keys to config/application.rb file

B. Use 'heroku config:set KEY=value' command

C. Store keys in a local .env file only

D. Push keys directly in your code files

Solution

1. Step 1: Understand environment variables on Heroku

   Heroku uses 'heroku config:set' to securely store environment variables like API keys.

2. Step 2: Evaluate other options

   Adding keys to config/application.rb or pushing keys in code risks exposure. Local .env files are not sent to Heroku.

3. Final Answer:

   Use 'heroku config:set KEY=value' command -> Option B

4. Quick Check:

   Set env vars securely with heroku config:set [OK]

Hint: Use heroku config:set to add env variables securely [OK]

Common Mistakes:

• Hardcoding keys in code risking leaks
• Relying on local .env files for Heroku
• Editing config/application.rb for secrets