Comprehensive Guide to Configuring Host and Port in Flask Development Server

Overview of Flask Development Server Configuration

Flask, as a lightweight Python web framework, typically uses its built-in development server during the development phase. However, many developers encounter confusion when configuring host and port with the flask run command, especially when they set app.run(host='0.0.0.0', port=3000) in their code but find flask run still uses the default 127.0.0.1:5000. This confusion stems from insufficient understanding of Flask's two distinct execution mechanisms.

Command-Line Parameter Configuration

The most direct method is specifying host and port through command-line parameters. Flask CLI provides -h and -p options to override default settings:

flask run -h localhost -p 3000

This approach takes effect immediately without modifying code or environment variables. The complete list of options, including other useful parameters like --reload for auto-reloading and --debugger for enabling the debugger, can be viewed using flask run --help.

Environment Variable Configuration

For scenarios requiring persistent configuration, environment variables FLASK_RUN_HOST and FLASK_RUN_PORT can be used:

export FLASK_RUN_HOST="127.0.0.1"
export FLASK_RUN_PORT=8000
flask run

On Windows systems, the corresponding setup commands are:

set FLASK_RUN_HOST=127.0.0.1
set FLASK_RUN_PORT=8000

The advantage of environment variables lies in their integration into deployment scripts or IDE configurations, ensuring consistency across development environments.

VS Code Debug Configuration

In integrated development environments like Visual Studio Code, debug parameters can be configured through the launch.json file:

{
  "name": "Python Debugger: Flask",
  "type": "debugpy",
  "request": "launch",
  "module": "flask",
  "env": {
    "FLASK_APP": "app.py",
    "FLASK_DEBUG": "1"
  },
  "args": [
    "run",
    "--host=0.0.0.0",
    "--port=3000",
    "--no-debugger",
    "--no-reload"
  ]
}

This configuration method is particularly suitable for team development, ensuring all members use identical server settings.

In-Depth Configuration Mechanism Analysis

The key to understanding Flask's configuration mechanism lies in distinguishing the different scopes of the flask run command and the app.run() method:

• flask run is an independent command provided by Flask CLI, running outside the application context and unable to access internal application configurations
• app.run() is a method of the Flask application instance, effective only when directly running Python scripts (i.e., python app.py)
• Setting the SERVER_NAME configuration item does not affect the flask run command, as the command cannot read application configurations

Security Considerations

While binding to 0.0.0.0 in development environments facilitates testing, it poses significant security risks:

• Development servers are not optimized for production environments, containing performance and security vulnerabilities
• Exposing development servers may allow attackers to access sensitive development data
• It is recommended to use 0.0.0.0 binding only in trusted network environments

Production Environment Deployment Recommendations

For production environments, professional WSGI servers must be used:

gunicorn -w 2 -b 0.0.0.0:3000 myapp:app

Other recommended production servers include uWSGI and mod_wsgi, offering better performance, security, and reliability.

Common Issue Resolution

Developers frequently encounter issues including port conflicts, insufficient permissions, and firewall restrictions:

• Port conflicts: Use netstat -an | grep 5000 to check port usage
• Permission issues: On Linux systems, ports below 1024 require root privileges
• Firewall configuration: Ensure firewalls allow inbound connections on specified ports

Best Practices Summary

Based on practical development experience, the following configuration strategies are recommended:

• Use localhost or 127.0.0.1 in development environments to ensure security
• Standardize environment variables or configuration files for team projects
• Strictly use professional WSGI servers in production environments
• Regularly check and update Flask and related dependency versions