Environment configuration files in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does Rails select environment configuration?

In a Rails app, when you run rails server without specifying an environment, which environment configuration file does Rails load by default?

A config/environments/development.rb

B config/environments/test.rb

C config/environments/production.rb

D config/application.rb

💡 Hint

Think about which environment is used when you start the server locally for development.

By default, Rails runs in the development environment when you start the server without specifying otherwise. So it loads config/environments/development.rb.

📝 Syntax

intermediate

Identify the syntax error in environment config

Which option contains a syntax error in a Rails environment configuration file?

Ruby on Rails

Example snippet:
Rails.application.configure do
  config.cache_classes = true
  config.eager_load = true
  config.consider_all_requests_local = false
end

A config.eager_load = true

B config.consider_all_requests_local = false end

C config.consider_all_requests_local = false

D config.cache_classes = true

💡 Hint

Look for misplaced keywords or missing line breaks.

Option B has end on the same line without proper separation, causing a syntax error.

❓ state_output

advanced

What is the value of config.cache_classes in test environment?

Given the default Rails environment files, what is the value of config.cache_classes in config/environments/test.rb?

A undefined

B false

C nil

D true

💡 Hint

Test environment is optimized for speed and consistency.

In the test environment, config.cache_classes is set to true to avoid reloading classes and speed up tests.

🔧 Debug

advanced

Why does Rails load wrong environment config?

You run rails server -e production but Rails still loads development settings. What is the most likely cause?

A Rails does not support -e flag for environment selection

B You forgot to restart the server after changing environment

C The RAILS_ENV environment variable is set to development overriding the flag

D config/environments/production.rb file is missing

💡 Hint

Environment variables have priority over command flags.

If the RAILS_ENV variable is set to development, it overrides the -e production flag, causing Rails to load development config.

🧠 Conceptual

expert

Why separate environment config files in Rails?

Why does Rails use separate files like development.rb, test.rb, and production.rb instead of one config file for all environments?

A To allow different settings optimized for each environment's needs and security

B Because Rails cannot parse a single file with multiple environment blocks

C To prevent sharing any configuration between environments

D To force developers to write more code and increase complexity

💡 Hint

Think about how development and production differ in purpose and constraints.

Separate files let Rails use tailored settings for development, testing, and production, improving performance, security, and debugging.

Practice

1. What is the main purpose of environment configuration files in a Rails application?

easy

A. To set different settings for development, test, and production environments

B. To store user data securely

C. To define database schemas

D. To write application business logic

Solution

1. Step 1: Understand environment files role

   Environment files in Rails are used to configure how the app behaves in different situations like development or production.

2. Step 2: Match purpose to options

   Only To set different settings for development, test, and production environments describes setting different configurations for each environment, which is the main purpose.

3. Final Answer:

   To set different settings for development, test, and production environments -> Option A

4. Quick Check:

   Environment files configure settings per environment [OK]

Hint: Think: different setups for dev, test, prod [OK]

Common Mistakes:

• Confusing environment files with database schema files
• Thinking environment files store user data
• Assuming business logic is set here

2. Which file path correctly points to the production environment configuration in a Rails app?

easy

A. config/production/environment.rb

B. config/environments/production.rb

C. config/environment/production.rb

D. config/environments.rb/production

Solution

1. Step 1: Recall Rails environment file location

   Rails stores environment configs inside the config/environments directory.

2. Step 2: Identify correct file name for production

   The production environment file is named production.rb inside that folder.

3. Final Answer:

   config/environments/production.rb -> Option B

4. Quick Check:

   Production config file path = config/environments/production.rb [OK]

Hint: Look for config/environments/[env].rb [OK]

Common Mistakes:

• Swapping folder and file names
• Using incorrect folder order
• Adding extra file extensions

3. Given this code in config/environments/development.rb:

Rails.application.configure do
  config.cache_classes = false
  config.eager_load = false
end

What effect does this configuration have when running the app in development?

medium

A. Eager loading loads all code at startup, slowing boot time

B. Classes are cached, improving performance but requiring server restart

C. Classes reload on each request, speeding up development changes

D. Caching is enabled, so data is stored permanently

Solution

1. Step 1: Understand config.cache_classes = false

   This means Rails reloads classes on every request, so code changes show immediately without restarting.

2. Step 2: Understand config.eager_load = false

   Eager loading off means Rails does not load all code at startup, which is typical for development to save boot time.

3. Final Answer:

   Classes reload on each request, speeding up development changes -> Option C

4. Quick Check:

   cache_classes false means reload classes each request [OK]

Hint: cache_classes false means reload code on every request [OK]

Common Mistakes:

• Confusing cache_classes false with caching data
• Thinking eager_load false means eager loading is on
• Assuming classes are cached in development

4. You added this line to config/environments/production.rb:

config.consider_all_requests_local = true

But you still don't see detailed error pages in production. What is the likely problem?

medium

A. Rails does not support detailed errors in production at all

B. The line should be in development.rb, not production.rb

C. You need to restart the server for changes to take effect

D. The setting is overridden by another config file or environment variable

Solution

1. Step 1: Understand consider_all_requests_local

   This setting controls if Rails shows detailed error pages. True means show detailed errors.

2. Step 2: Check why it might not work in production

   Often other configs or environment variables override this setting, preventing detailed errors.

3. Final Answer:

   The setting is overridden by another config file or environment variable -> Option D

4. Quick Check:

   Overridden config blocks detailed errors [OK]

Hint: Check for overrides or env variables blocking changes [OK]

Common Mistakes:

• Assuming detailed errors never show in production
• Not restarting server after config changes
• Putting setting in wrong environment file

5. You want to disable asset debugging only in the test environment without affecting development or production. Which change correctly achieves this in Rails?

medium

A. Add config.assets.debug = false inside config/environments/test.rb

B. Add config.assets.debug = false inside config/environments/production.rb

C. Add config.assets.debug = false inside config/application.rb

D. Add config.assets.debug = false inside config/environments/development.rb

Solution

1. Step 1: Identify environment-specific config location

   To change behavior only in test, put config in config/environments/test.rb.

2. Step 2: Set assets.debug to false in test environment

   Adding config.assets.debug = false in test.rb disables asset debugging only for tests.

3. Final Answer:

   Add config.assets.debug = false inside config/environments/test.rb -> Option A

4. Quick Check:

   Environment-specific config goes in matching environment file [OK]

Hint: Put config in matching environment file to isolate changes [OK]

Common Mistakes:

• Changing config in wrong environment file
• Changing config in application.rb affects all environments
• Forgetting to restart server after changes