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.