Environment configuration files in Ruby on Rails - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to load environment variables from the .env file using dotenv gem.

Ruby on Rails

require 'dotenv'\nDotenv.[1]

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

Aread

Bload

Copen

Dfetch

Attempts:

3 left

💡 Hint

Common Mistakes

Using methods like read or open which do not load environment variables.

Forgetting to require the dotenv gem before calling its methods.

The Dotenv.load method loads environment variables from the .env file into the application environment.

2fill in blank

medium

Complete the code to access the Rails environment configuration for the current environment.

Ruby on Rails

Rails.application.config_for(:[1])

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

Aenvironment

Bdatabase

Csecrets

Dcredentials

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing environment with database or secrets configuration.

Using incorrect symbols that do not match config files.

The config_for(:environment) method loads configuration specific to the current Rails environment (like development, test, or production).

3fill in blank

hard

Fix the error in the code to correctly fetch a configuration value from credentials.

Ruby on Rails

Rails.application.credentials.[1]

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

Afetch(:api_key)

Bread(:api_key)

Cget(:api_key)

Dapi_key

Attempts:

3 left

💡 Hint

Common Mistakes

Using fetch or get which are not valid methods on credentials.

Trying to read credentials like a hash instead of method calls.

Accessing credentials uses method calls like Rails.application.credentials.api_key without fetch or get methods.

4fill in blank

hard

Fill both blanks to define a custom configuration in config/application.rb and access it in the app.

Ruby on Rails

module MyApp\n  class Application < Rails::Application\n    config.[1] = 'value'\n  end\nend\n\nRails.application.config.[2]

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

Acustom_setting

Bcustom_value

Dcustom_config

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for setting and accessing the config.

Trying to access config with incorrect method names.

You define a custom config key like config.custom_setting and access it the same way with Rails.application.config.custom_setting.

5fill in blank

hard

Fill all three blanks to create a YAML environment config file and load a value in Rails.

Ruby on Rails

development:\n  api_key: [1]\n\nconfig = Rails.application.config_for(:[2])\nputs config[:[3]]

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

A'123abc'

Benvironment

Capi_key

D'secret'

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong file name in config_for.

Accessing config keys as strings instead of symbols.

Incorrect YAML syntax for the api_key value.

The YAML file defines api_key: '123abc' under development. Then config_for(:environment) loads it, and config[:api_key] accesses the key.

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