Why deployment preparation matters in Ruby on Rails - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the Rails environment to production before deployment.

Ruby on Rails

Rails.env = '[1]'

Drag options to blanks, or click blank then click option'

Aproduction

Bdevelopment

Ctest

Dstaging

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'development' instead of 'production' causes the app to run with debug settings.

Forgetting to set the environment can lead to unexpected behavior.

Setting Rails.env to production ensures the app runs with production settings during deployment.

2fill in blank

medium

Complete the code to precompile assets before deployment.

Ruby on Rails

rails assets:[1]

Drag options to blanks, or click blank then click option'

Abuild

Bclean

Ccompile

Dprecompile

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'compile' instead of 'precompile' will cause errors.

Skipping asset precompilation can slow down the app.

Running rails assets:precompile prepares CSS and JavaScript files for production.

3fill in blank

hard

Fix the error in the database configuration for production.

Ruby on Rails

production:
  adapter: postgresql
  encoding: unicode
  database: myapp_[1]
  pool: 5
  username: myapp
  password: <%= ENV['MYAPP_DATABASE_PASSWORD'] %>

Drag options to blanks, or click blank then click option'

Aproduction

Btest

Cdevelopment

Dstaging

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'development' or 'test' database names in production causes connection errors.

Not matching the environment name leads to wrong database usage.

The production database name should include 'production' to match the environment.

4fill in blank

hard

Fill both blanks to configure the secret key base for production.

Ruby on Rails

production:
  secret_key_base: <%= ENV['[1]'] %>
  host: '[2]'

Drag options to blanks, or click blank then click option'

ASECRET_KEY_BASE

BDATABASE_URL

Cexample.com

Dlocalhost

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'DATABASE_URL' instead of 'SECRET_KEY_BASE' for the secret key.

Setting host to 'localhost' instead of the real domain.

The secret key base is stored in the environment variable SECRET_KEY_BASE. The host should be the live domain like example.com.

5fill in blank

hard

Fill all three blanks to create a safe deployment script snippet.

Ruby on Rails

namespace :deploy do
  task :restart do
    on roles(:app) do
      execute :touch, '[1]/tmp/restart.[2]'
    end
  end
  after :publishing, :restart
  after :restart, :clear_cache do
    on roles(:web), in: :groups, limit: 3, wait: 10 do
      within '[3]' do
        execute :rake, 'cache:clear'
      end
    end
  end
end

Drag options to blanks, or click blank then click option'

Acurrent

Btxt

C/var/www/myapp

Dlog

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'log' instead of 'current' for the restart path.

Using 'txt' incorrectly or missing the file extension.

Setting the path to 'log' instead of the app folder.

The touch command updates tmp/restart.txt inside the current folder to restart the app. The cache clear runs inside the app folder /var/www/myapp.

Practice

1. Why is it important to precompile assets before deploying a Rails application?

easy

A. To improve loading speed by preparing CSS and JavaScript files in advance

B. To automatically fix bugs in the application code

C. To create database tables needed for the app

D. To backup user data before deployment

Solution

1. Step 1: Understand what asset precompilation does

   Precompiling assets means preparing CSS and JavaScript files so browsers can load them faster.

2. Step 2: Identify the benefit during deployment

   This step reduces load time and avoids delays when users visit the app.

3. Final Answer:

   To improve loading speed by preparing CSS and JavaScript files in advance -> Option A

4. Quick Check:

   Precompile assets = faster page load [OK]

Hint: Precompile assets to speed up user page loads [OK]

Common Mistakes:

• Thinking precompilation fixes code bugs
• Confusing asset precompilation with database setup
• Assuming it backs up data

2. Which command is used to migrate the database schema during Rails deployment?

easy

A. rails db:seed

B. rails server

C. rails assets:precompile

D. rails db:migrate

Solution

1. Step 1: Identify the command for database schema changes

   The command rails db:migrate applies changes to the database structure.

2. Step 2: Differentiate from other commands

   rails db:seed adds data, rails assets:precompile prepares assets, and rails server starts the app server.

3. Final Answer:

   rails db:migrate -> Option D

4. Quick Check:

   Database schema update = rails db:migrate [OK]

Hint: Use db:migrate to update database schema [OK]

Common Mistakes:

• Confusing db:seed with db:migrate
• Using assets:precompile for database tasks
• Running rails server instead of migration

3. What will happen if you deploy a Rails app without running rails assets:precompile?

medium

A. The app will crash immediately on startup

B. The app will load assets slower or show missing styles and scripts

C. The database will not update with new tables

D. User data will be lost during deployment

Solution

1. Step 1: Understand the role of asset precompilation

   Without precompiling, CSS and JavaScript files are not optimized for production.

2. Step 2: Predict the user experience

   This causes slow loading or missing styles/scripts, but the app still runs.

3. Final Answer:

   The app will load assets slower or show missing styles and scripts -> Option B

4. Quick Check:

   Missing precompile = slow or broken assets [OK]

Hint: No precompile means broken or slow assets [OK]

Common Mistakes:

• Thinking the app crashes immediately
• Confusing asset issues with database problems
• Assuming user data loss

4. You forgot to run rails db:migrate before deployment. What problem will most likely occur?

medium

A. The app will show errors when trying to access new database columns or tables

B. The app will load assets incorrectly

C. The server will refuse to start

D. The app will automatically migrate the database

Solution

1. Step 1: Identify the effect of missing migrations

   Without running migrations, the database schema is outdated and missing new columns or tables.

2. Step 2: Understand app behavior

   When the app tries to use these missing parts, it will raise errors.

3. Final Answer:

   The app will show errors when trying to access new database columns or tables -> Option A

4. Quick Check:

   Missing migration = database access errors [OK]

Hint: Always run db:migrate before deployment [OK]

Common Mistakes:

• Thinking assets will fail due to missing migration
• Assuming server won't start
• Believing Rails auto-migrates on deploy

5. You want to deploy a Rails app with a new feature that requires database changes and updated assets. Which sequence of commands should you run before deployment?

hard

A. restart server, rails db:migrate, rails assets:precompile

B. rails assets:precompile, restart server, rails db:migrate

C. rails db:migrate, rails assets:precompile, restart server

D. rails db:seed, rails assets:precompile, restart server

Solution

1. Step 1: Apply database changes first

   Run rails db:migrate to update the database schema before starting the app.

2. Step 2: Precompile assets after migration

   Run rails assets:precompile to prepare CSS and JS files for production.

3. Step 3: Restart the server to apply changes

   Restarting the server loads the new code, database, and assets.

4. Final Answer:

   rails db:migrate, rails assets:precompile, restart server -> Option C

5. Quick Check:

   Migration then precompile then restart = correct deploy steps [OK]

Hint: Migrate DB, precompile assets, then restart server [OK]

Common Mistakes:

• Running precompile before migration
• Restarting server before migration
• Using db:seed instead of db:migrate