如何将本地运行的Flask API部署到Web服务器以实现公网访问？

Hey there! Let's get your Flask API up and running on Apache properly. I've helped folks troubleshoot this exact issue plenty of times, so let's break it down step by step.

First, let's start with the basics—since your app works locally, the issue is almost certainly with Apache's configuration or deployment structure, not your Flask code itself.

Step 1: Prepare Your App for Apache Deployment #

Your current single-script setup works locally, but Apache needs a more structured layout to serve it correctly:

1. Create a dedicated project folder on your server (e.g., /var/www/FlaskDocManager/).
2. Move your existing Flask code into a file named app.py inside this folder (keep all your route logic intact).
3. Add a wsgi.py file in the same folder—this acts as the bridge between Apache and your Flask app:

import sys
sys.path.insert(0, '/var/www/FlaskDocManager')

from app import app as application  # Apache looks for the 'application' variable by default

Step 2: Use a Virtual Environment (Critical!) #

Running your app in a virtual environment ensures Apache uses the correct dependencies (no conflicts with system Python packages):

• In your project folder, create the virtual env:

  python3 -m venv venv
  

• Activate it and install your dependencies:

  source venv/bin/activate
  pip install flask
  # Install any other packages your document manager needs here
  deactivate
  

Step 3: Configure Apache's Virtual Host #

Create a new Apache config file (e.g., /etc/apache2/sites-available/flask_doc_manager.conf) with these settings:

<VirtualHost *:80>
    ServerName your-server-ip-or-domain  # Replace with your public IP/domain
    ServerAdmin your-email@example.com

    # Tell Apache about your virtual env and project path
    WSGIDaemonProcess FlaskDocManager python-home=/var/www/FlaskDocManager/venv python-path=/var/www/FlaskDocManager
    WSGIScriptAlias / /var/www/FlaskDocManager/wsgi.py

    # Grant Apache access to your project folder
    <Directory /var/www/FlaskDocManager>
        WSGIProcessGroup FlaskDocManager
        WSGIApplicationGroup %{GLOBAL}
        Require all granted
    </Directory>

    # Log files for debugging
    ErrorLog ${APACHE_LOG_DIR}/flask_doc_error.log
    CustomLog ${APACHE_LOG_DIR}/flask_doc_access.log combined
</VirtualHost>

Step 4: Enable the Site & Restart Apache #

Run these commands to apply your changes:

• Enable the new site: sudo a2ensite flask_doc_manager.conf
• Disable the default Apache site if needed: sudo a2dissite 000-default.conf
• Enable mod_wsgi (the Apache-Flask bridge): sudo a2enmod wsgi
• Restart Apache: sudo systemctl restart apache2

Troubleshooting Your /runDocumentManager Endpoint #

Since your endpoint uses request.args.get('input_path'), keep these in mind:

• The Apache user (usually www-data) needs read permissions to any directory you pass via the input_path parameter. Fix this with:

  sudo chmod -R 755 /your/target-directory
  # Or add www-data to the directory's group:
  sudo chown -R :www-data /your/target-directory
  

• Avoid relative paths in your app—use absolute file paths to prevent Apache from looking in the wrong directory.

If It Still Fails: Check the Logs #

Always check Apache's error logs first for specific issues:

sudo tail -f /var/log/apache2/flask_doc_error.log

Common issues here include missing dependencies, typos in config files, or permission errors.

内容的提问来源于stack exchange，提问作者Mousam Singh