Managing Application Configuration in Flask Using the Config Class

Flask applications often require different configuration settings for various environments, such as toggling debug mode or setting secret keys. The Config class, accessible via app.config , serves as a flexible, dict‑like base for managing these settings.

When a Flask app is instantiated, app.config is an instance of flask.config.Config , which inherits from dict , allowing the use of all standard dictionary methods.

Configuration can be set directly:

app.config['DEBUG'] = True

Multiple values can be updated at once:

app.config.update(
    DEBUG=True,
    SECRET_KEY='af176072121a1f1c9cf7a8c58364535ebfd75865'
)

Flask also provides several helper methods to load configurations from various sources:

app.config.from_object() – loads from a Python object, module, or class.

app.config.from_pyfile('config.py') – loads from a Python file.

app.config.from_envvar('CONFIG_PATH') – loads from a file path specified in an environment variable.

app.config.from_json('config.json') – loads from a JSON file.

app.config.from_mapping({'DEBUG': True}) – loads from a mapping or keyword arguments.

Passing a config dictionary directly to the Flask constructor, e.g. Flask(__name__, config={'DEBUG': True, 'SECRET_KEY': '...'} ) .

Typical usage involves defining a base configuration class in config.py and loading environment‑specific subclasses via from_object , often combined with OS environment variables accessed through os.getenv() or os.environ.get() . On Windows, changes to environment variables require a system reboot to take effect.

Overall, the Config class offers a versatile and clean way to manage Flask application settings, supporting inheritance, multiple loading strategies, and seamless integration with environment variables.