Environment-based configuration in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is environment-based configuration in Flask?

It means setting up your Flask app to use different settings depending on where it runs, like development, testing, or production. This helps keep things organized and safe.

beginner

How do you tell Flask to use a specific configuration file?

You use app.config.from_object() or app.config.from_pyfile() to load settings from a Python file or object that matches your environment.

beginner

Why should you avoid hardcoding sensitive info like passwords in your Flask config?

Because hardcoding secrets can expose them if your code is shared. Instead, use environment variables or separate config files that are not shared publicly.

intermediate

What is the purpose of the FLASK_ENV environment variable?

It tells Flask which environment it is running in, like 'development' or 'production', so Flask can adjust settings like debug mode automatically.

intermediate

How can you switch configurations without changing your code in Flask?

By setting environment variables outside your code, like FLASK_ENV or custom variables, and loading config based on those variables.

Which Flask method loads configuration from a Python file?

A app.set_config()

B app.load_config()

C app.config.from_pyfile()

D app.config.load()

app.config.from_pyfile() loads configuration from a Python file.

What does setting FLASK_ENV=production do in Flask?

A Disables debug mode and optimizes for production

B Starts the Flask shell

C Runs tests automatically

D Enables debug mode

Setting FLASK_ENV=production disables debug mode and optimizes Flask for production use.

Why use environment variables for configuration?

A To hardcode secrets in code

B To keep sensitive info out of code and easily change settings

C To slow down the app

D To avoid using config files

Environment variables keep sensitive info out of code and allow easy changes without code edits.

Which is NOT a common Flask environment?

A development

B testing

C production

D debugging

'debugging' is not a standard Flask environment; common ones are development, testing, and production.

How can you load different configs based on environment in Flask?

A Use if-else in code checking environment variables

B Use the same config for all environments

C Manually edit config files every time

D Flask does not support environment-based configs

You can check environment variables in your code and load different configs accordingly.

Explain how environment-based configuration helps in Flask app development and deployment.

Think about why you wouldn't want the same settings everywhere.

Describe how to set up and switch between multiple configuration files in a Flask app.

Consider how your app knows which config to use.

Practice

1. What is the main reason to use environment-based configuration in a Flask app?

easy

A. To avoid using environment variables completely

B. To write all configuration directly in the main app file

C. To separate settings for development, testing, and production environments

D. To hardcode sensitive data like passwords in the code

Solution

1. Step 1: Understand environment-based configuration purpose

   It helps keep different settings for development, testing, and production separate and secure.

2. Step 2: Identify best practice for config management

   Separating configs avoids hardcoding sensitive data and makes the app flexible across environments.

3. Final Answer:

   To separate settings for development, testing, and production environments -> Option C

4. Quick Check:

   Environment-based config = Separate settings [OK]

Hint: Think about keeping dev and prod settings separate [OK]

Common Mistakes:

• Hardcoding all config in one file
• Ignoring environment differences
• Storing secrets in code
• Not using environment variables

2. Which of the following is the correct way to load configuration from a Python class in Flask?

easy

A. app.config.from_object('config.DevelopmentConfig')

B. app.config.from_file('config.py')

C. app.load_config('config.py')

D. app.config.load('DevelopmentConfig')

Solution

1. Step 1: Recall Flask config loading methods

   Flask uses from_object to load config from a Python class.

2. Step 2: Match correct syntax

   app.config.from_object('config.DevelopmentConfig') correctly loads the class named DevelopmentConfig from config module.

3. Final Answer:

   app.config.from_object('config.DevelopmentConfig') -> Option A

4. Quick Check:

   Use from_object to load class config [OK]

Hint: Use from_object with full class path string [OK]

Common Mistakes:

• Using non-existent methods like from_file or load_config
• Passing filename instead of class path
• Missing quotes around class path
• Confusing from_object with from_envvar

3. Given this Flask config setup:

class Config:
    DEBUG = False

class DevelopmentConfig(Config):
    DEBUG = True

app = Flask(__name__)
app.config.from_object(DevelopmentConfig)
print(app.config['DEBUG'])

What will be printed?

medium

A. False

B. KeyError

C. None

D. True

Solution

1. Step 1: Understand class inheritance

   DevelopmentConfig inherits from Config and overrides DEBUG to True.

2. Step 2: Check which config is loaded

   app.config.from_object loads DevelopmentConfig, so DEBUG is True.

3. Final Answer:

   True -> Option D

4. Quick Check:

   Subclass overrides DEBUG = True [OK]

Hint: Subclass config overrides parent values [OK]

Common Mistakes:

• Assuming base class value is used
• Confusing attribute names
• Expecting KeyError for existing keys
• Ignoring inheritance

4. What is wrong with this Flask config loading code?

app = Flask(__name__)
app.config.from_envvar('MY_CONFIG')

Assuming the environment variable MY_CONFIG is not set.

medium

A. It will silently ignore missing MY_CONFIG and use default config

B. It will raise a RuntimeError because MY_CONFIG is missing

C. It will load config from a file named 'MY_CONFIG'

D. It will load config from environment variables automatically

Solution

1. Step 1: Understand from_envvar behavior

   from_envvar expects an environment variable with a filepath; if missing, it raises RuntimeError.

2. Step 2: Check what happens if MY_CONFIG is not set

   Since MY_CONFIG is missing, Flask raises RuntimeError to alert missing config file.

3. Final Answer:

   It will raise a RuntimeError because MY_CONFIG is missing -> Option B

4. Quick Check:

   Missing env var causes RuntimeError [OK]

Hint: from_envvar requires env var set or it errors [OK]

Common Mistakes:

• Assuming it ignores missing env var
• Thinking it loads from env vars automatically
• Confusing from_envvar with from_object
• Expecting silent fallback to defaults

5. You want your Flask app to load different configs based on the environment variable FLASK_ENV. Which code snippet correctly implements this?

hard

A. if os.getenv('FLASK_ENV') == 'production':
app.config.from_object('config.ProductionConfig')
else:
app.config.from_object('config.DevelopmentConfig')

B. app.config.from_object('config.' + FLASK_ENV + 'Config')

C. app.config.from_envvar('FLASK_ENV')

D. app.config.from_object('config.DefaultConfig')

Solution

1. Step 1: Check how to read environment variable

   Use os.getenv('FLASK_ENV') to get the current environment string.

2. Step 2: Use conditional logic to load correct config

   If environment is 'production', load ProductionConfig; otherwise load DevelopmentConfig.

3. Final Answer:

   if os.getenv('FLASK_ENV') == 'production': app.config.from_object('config.ProductionConfig') else: app.config.from_object('config.DevelopmentConfig') -> Option A

4. Quick Check:

   Use os.getenv + if-else to select config [OK]

Hint: Use os.getenv and if-else to pick config class [OK]

Common Mistakes:

• Trying to concatenate string without quotes
• Using from_envvar with FLASK_ENV directly
• Not handling default environment
• Loading only one config regardless of env