ผลักบริบทในสคริปต์และเชลล์

Sometimes you run Flask code with no request, like a script that seeds the database. There is no context, so the usual proxies fail.

Run such code and Flask raises RuntimeError: working outside of application context. It is telling you no app context is active.

Fix it by pushing one with app.app_context(). Wrap your code in a with block and current_app starts working again.

Entering the with block pushes the context, and leaving it pops the context. You never have to clean up by hand.

Inside the block, extensions bound to the app behave normally. You can run db.create_all() or query models from a plain script.

To exercise code that reads request, push a test request context with test_request_context instead of an app context.

The flask shell command opens a Python shell with an app context already pushed, so you can poke at your app interactively.

Custom flask commands you register also run inside an app context automatically, so seed and admin scripts just work.

Pick by need: use app_context when you only touch the app or database, and a request context when your code reads request data.

Push contexts in a tight with block, not for the whole script. Smaller scope means clearer code and predictable teardown.

Pushing contexts lets you reuse app logic in migrations, cron jobs, and tests, not just inside live web requests.

Let us nail the fix for the context error.

No request? Push one. Use app_context for app and database work, test_request_context for request data, and let flask shell handle it for you. 🎉