Database setup for production in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the config/database.yml file in a Rails production setup?

It defines the database connection settings for different environments, including production. This file tells Rails how to connect to the production database with details like adapter, host, username, password, and database name.

beginner

Why should you avoid using SQLite in a Rails production environment?

SQLite is designed for simple, local development and does not handle multiple users or heavy traffic well. Production environments usually use more robust databases like PostgreSQL or MySQL that support concurrency and scaling.

beginner

What command do you run to create the production database in Rails?

You run RAILS_ENV=production rails db:create to create the production database using the settings in config/database.yml.

beginner

How do you run migrations on the production database in Rails?

Use RAILS_ENV=production rails db:migrate. This applies all pending database changes to the production database.

intermediate

What is the role of environment variables in Rails production database setup?

Environment variables store sensitive info like database passwords outside the code. Rails can read these variables to keep secrets safe and allow easy changes without editing code files.

Which database adapter is commonly recommended for Rails production?

A MongoDB

B SQLite

C CSV files

D PostgreSQL

PostgreSQL is a powerful, reliable database that works well with Rails in production.

What does RAILS_ENV=production rails db:create do?

A Creates the development database

B Creates the test database

C Creates the production database

D Deletes the production database

This command creates the production database using the production settings.

Where should you store your production database password in Rails?

A In environment variables

B Hardcoded in <code>database.yml</code>

C In a public GitHub repo

D In the app's JavaScript files

Environment variables keep sensitive info safe and separate from code.

Which command runs database migrations in production?

A RAILS_ENV=production rails db:migrate

B rails db:migrate

C rails db:rollback

D rails server

Adding RAILS_ENV=production runs migrations on the production database.

Why is SQLite not suitable for production in Rails?

A It is too fast

B It does not support multiple users well

C It requires internet connection

D It is not free

SQLite is designed for simple, local use and struggles with concurrent users.

Explain the steps to set up a production database in a Rails application.

Think about configuration, security, and commands.

Why is it important to separate production database credentials from your code in Rails?

Consider risks of hardcoding secrets.

Practice

1. What file do you edit to configure your production database settings in a Rails app?

easy

A. config/initializers/database.rb

B. config/routes.rb

C. config/environments/production.rb

D. config/database.yml

Solution

1. Step 1: Identify the configuration file for databases

   Rails uses config/database.yml to set up database connections for all environments including production.

2. Step 2: Confirm production environment settings location

   The production database details like adapter, username, password, and host are specified inside config/database.yml under the production section.

3. Final Answer:

   config/database.yml -> Option D

4. Quick Check:

   Production DB config = config/database.yml [OK]

Hint: Production DB settings are always in database.yml [OK]

Common Mistakes:

• Confusing environment config files with database config
• Editing routes.rb for database settings
• Looking in initializers for DB config

2. Which command correctly sets up the production database in Rails?

easy

A. rails db:migrate RAILS_ENV=production

B. rails db:create RAILS_ENV=production

C. rails db:setup RAILS_ENV=production

D. rails db:seed RAILS_ENV=production

Solution

1. Step 1: Understand the purpose of each command

   db:create creates the database, db:migrate runs migrations, db:seed loads seed data, and db:setup does all three: create, migrate, and seed.

2. Step 2: Choose the command that fully prepares the production DB

   To fully prepare the production database, including creation, migration, and seeding, use rails db:setup RAILS_ENV=production.

3. Final Answer:

   rails db:setup RAILS_ENV=production -> Option C

4. Quick Check:

   Full DB setup = rails db:setup [OK]

Hint: Use db:setup to create, migrate, and seed at once [OK]

Common Mistakes:

• Using db:create alone without migrations
• Running db:migrate without creating DB first
• Forgetting to specify RAILS_ENV=production

3. Given this config/database.yml snippet for production:

production:
  adapter: postgresql
  encoding: unicode
  database: myapp_production
  pool: 5
  username: user123
  password: secret
  host: db.example.com

What will happen if you run rails db:setup RAILS_ENV=production?

medium

A. It creates the production database, runs migrations, and loads seed data using the given credentials.

B. It only creates the database but does not run migrations or seed data.

C. It throws an error because the host is not localhost.

D. It ignores the production section and uses development settings instead.

Solution

1. Step 1: Understand db:setup behavior with production config

   The command rails db:setup RAILS_ENV=production reads the production section in database.yml and uses those credentials to create the DB, run migrations, and seed data.

2. Step 2: Confirm host usage and environment selection

   Using a remote host like db.example.com is valid if accessible. The command will not default to development but use production as specified.

3. Final Answer:

   It creates the production database, runs migrations, and loads seed data using the given credentials. -> Option A

4. Quick Check:

   db:setup uses production config fully [OK]

Hint: db:setup uses production config fully, even remote hosts [OK]

Common Mistakes:

• Assuming db:setup only creates DB without migrations
• Thinking host must be localhost
• Forgetting to specify RAILS_ENV=production

4. You run rails db:setup RAILS_ENV=production but get a connection error. Which is the most likely cause?

medium

A. You ran the command without RAILS_ENV=production.

B. The config/database.yml production section has wrong credentials or unreachable host.

C. The production database already exists.

D. You forgot to run rails db:migrate first.

Solution

1. Step 1: Analyze connection error causes

   Connection errors usually mean the app cannot reach the database server or the credentials are invalid.

2. Step 2: Check command and environment usage

   Running rails db:setup creates and migrates the DB, so missing migrations or existing DB are unlikely causes of connection errors.

3. Final Answer:

   The config/database.yml production section has wrong credentials or unreachable host. -> Option B

4. Quick Check:

   Connection error = wrong credentials or host [OK]

Hint: Connection errors usually mean bad credentials or host [OK]

Common Mistakes:

• Assuming migrations cause connection errors
• Ignoring environment variable in command
• Thinking existing DB causes connection failure

5. You want to securely manage your production database credentials without hardcoding them in config/database.yml. Which approach is best practice?

hard

A. Use environment variables referenced in database.yml for username and password.

B. Store credentials in plain text inside database.yml but restrict file permissions.

C. Commit encrypted credentials directly in database.yml without decryption setup.

D. Remove username and password from database.yml and rely on default system user.

Solution

1. Step 1: Understand secure credential management

   Hardcoding sensitive info in files is risky. Using environment variables keeps secrets out of code and config files.

2. Step 2: Confirm best practice in Rails

   Rails supports referencing environment variables in database.yml like <%= ENV['DB_USERNAME'] %> for secure, flexible credential management.

3. Final Answer:

   Use environment variables referenced in database.yml for username and password. -> Option A

4. Quick Check:

   Env vars for DB credentials = best practice [OK]

Hint: Use ENV vars in database.yml to keep credentials safe [OK]

Common Mistakes:

• Hardcoding passwords in config files
• Committing encrypted data without decryption
• Relying on system defaults without credentials