Database setup for production in Ruby on Rails - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create the production database in Rails.

Ruby on Rails

rails db:[1] RAILS_ENV=production

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

Acreate

Brollback

Cseed

Dmigrate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'migrate' before creating the database causes errors.

Using 'seed' tries to add data but the database must exist first.

Use create to make the production database before running migrations.

2fill in blank

medium

Complete the code to apply migrations to the production database.

Ruby on Rails

rails db:[1] RAILS_ENV=production

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

Arollback

Bseed

Cmigrate

Dcreate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'create' again after the database exists is unnecessary.

Using 'rollback' reverses migrations instead of applying them.

The migrate command applies all pending migrations to update the database schema.

3fill in blank

hard

Fix the error in the command to seed the production database.

Ruby on Rails

rails db:[1] RAILS_ENV=production

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

Amigrate

Brollback

Ccreate

Dseed

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'migrate' tries to change schema, not add data.

Using 'create' tries to make a new database, not add data.

Use seed to load initial data into the production database after migrations.

4fill in blank

hard

Fill both blanks to configure the production database adapter and username in config/database.yml.

Ruby on Rails

production:
  adapter: [1]
  username: [2]

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

Apostgresql

Bmysql2

Croot

Dadmin

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'mysql2' adapter when the project uses PostgreSQL.

Using 'root' username which is less secure for production.

Production often uses postgresql as adapter and admin as username for database access.

5fill in blank

hard

Fill all three blanks to set the production database host, password, and database name in config/database.yml.

Ruby on Rails

production:
  host: [1]
  password: [2]
  database: [3]

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

Alocalhost

Bsecurepass123

Cmyapp_production

D127.0.0.1

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'localhost' instead of '127.0.0.1' can sometimes cause connection issues.

Using weak or empty passwords.

Using wrong database names that don't match the environment.

The host is usually 127.0.0.1 for local production servers, the password is a secure string, and the database name follows the app name with _production.