ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #flask
Learn how Flask’s application factory pattern isolates configuration, prevents state leakage between tests, and enables lazy extension setup with a concrete, step‑by‑step example.
Architecture note on using Flask Blueprints with an application factory: requirements, minimal design, trust boundaries, operational checks, failure modes and verification steps.
The goal is to migrate a Flask application to a new version without downtime by adjusting NGINX upstream weights between two identical Gunicorn worker pools while preserving Flask‑signed cookie sessions. Constraints include the possibility that Gunicorn’s graceful reload (HUP) may terminate workers before long‑running requests finish, and that session contin
Following the tutorial here I have the following 2 files: app.py from flask import Flask, request app = Flask(__name__) @app.route('/', methods=['GET']) def hello(): """Return a friendly HTTP greeting.""" who = request.args.get('who', 'World') return f'Hello {who}!\n' if __name__ == '__main__': # Used when running locally only. When deploying to Cloud Run, #
The goal is to decide whether Flask should automatically disable the Werkzeug debugger when the application detects it is likely running in a production‑exposed configuration, such as binding to 0.0.0.0 or operating behind a reverse proxy, while preserving the debugging experience for local development. Constraints include maintaining backward compatibility
Flask Request Timeout Handling in Development Server Flask's built-in development server, powered by Werkzeug, lacks native support for configuring request timeouts through application code. While production WSGI servers like Gunicorn provide timeout parameters to terminate long-running requests, this capability is absent in the development environment. The
Goal: Ensure that Flask user sessions remain valid across application restarts when moving from a local development setup to a production environment. Constraint: If the SECRET_KEY configuration is omitted, Flask generates a new random key on each process start, which invalidates existing session cookies; local tests may not reveal the problem when server‑si
Reproducible Development with Flask When building a Flask application, developers often isolate dependencies in a Python virtual environment to guarantee that the same package set runs across machines. The standard workflow is to activate the venv, set FLASK_APP and FLASK_ENV , and launch the app with flask run . This yields a lightweight development server
Goal To guarantee that a database schema change in a Flask 2.x application can be rolled back without data loss or orphaned columns. Constraint Column type changes and other non‑trivial alterations often require custom logic. Alembic’s autogenerate may miss these, while manual SQL scripts lack an automatic reverse path unless explicitly written. Uncertainty
nginx
python