Skip to content

Flask app DEBUG shouldn't be True always #4

@sysr-q

Description

@sysr-q

This leads to - as shown in #2 - the clients getting more information than they should really care or know about.
Debugging is fine for development, but you shouldn't leave it on for production.

You could perhaps do something like: app.debug = bool(os.environ.get("FLASK_DEBUG", 0)) or something similar, so that you can run it as FLASK_DEBUG=1 python __main__.py, or how-ever you so desire.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions