Database setup for production in Ruby on Rails - Step-by-Step Execution

Concept Flow - Database setup for production

Create production database config

↓

Run database creation command

↓

Run database migrations

↓

Verify database connection

↓

Start application with production DB

This flow shows the steps to prepare a Rails app's database for production use.

Execution Sample

Ruby on Rails

RAILS_ENV=production rails db:create
RAILS_ENV=production rails db:migrate
rails server -e production

Commands to create and migrate the production database, then start the server using it.

Execution Table

Step	Command	Action	Result	Notes
1	Check config/database.yml	Read production DB settings	Settings loaded	Ensure correct adapter, database, username, password
2	RAILS_ENV=production rails db:create	Create production DB	Database created	DB server must be accessible
3	RAILS_ENV=production rails db:migrate	Run migrations	Schema updated	Tables and columns created
4	Verify connection	Test DB queries	Queries succeed	Confirms DB setup is correct
5	rails server -e production	Start server	Server running with production DB	App connected to production DB
6	-	Exit	Setup complete	Ready for production use

💡 All steps completed successfully, production database is ready.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
production_database	not created	created	migrated	ready	ready
db_connection	none	none	none	active	active

Key Moments - 3 Insights

Why do we specify RAILS_ENV=production before commands?

This tells Rails to use the production database settings from config/database.yml, as shown in execution_table step 2 and 3.

What happens if the database server is not accessible during db:create?

The command will fail to create the database, stopping setup early as seen in execution_table step 2.

Why run migrations after creating the database?

Migrations set up the tables and schema needed by the app, shown in execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution table, what is the result after running 'RAILS_ENV=production rails db:create'?

A Schema updated

B Database created

C Server running

D Settings loaded

💡 Hint

Check execution_table row 2 under Result column.

At which step does the application start using the production database?

A Step 2

B Step 3

C Step 5

D Step 4

💡 Hint

Look at execution_table step 5 where the server starts.

If the database connection is not active after step 5, what is likely the problem?

A Server not started with production environment

B Database not created

C Migrations not run

D Config file missing

💡 Hint

Refer to variable_tracker db_connection status after step 5.

Concept Snapshot

Database setup for production in Rails:
1. Configure production DB in config/database.yml
2. Run 'RAILS_ENV=production rails db:create' to create DB
3. Run 'RAILS_ENV=production rails db:migrate' to apply schema
4. Verify connection and queries
5. Start server with 'rails server -e production'
This ensures your app uses the correct production database.

Full Transcript

To set up a Rails database for production, first ensure your config/database.yml has the correct production settings. Then run 'RAILS_ENV=production rails db:create' to create the production database. Next, run 'RAILS_ENV=production rails db:migrate' to apply all migrations and set up tables. Verify the connection by running queries. Finally, start your Rails server with 'rails server -e production' to connect to the production database. This process prepares your app to use the production database safely and correctly.

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