如何基于原生Python在Apache2部署含C/C++绑定依赖的Django应用

Got it, let's work through deploying your Django app (which relies on C/C++-based Python bindings) to Apache2 using your system's native Python environment—no virtualenv needed. Here's how to adjust your setup step by step:

1. Ensure Dependencies Are Installed in Native Python #

First, make sure all your project dependencies—including that C/C++-based Python binding library—are installed directly into your system's native Python site-packages directory.

• For Python 2.7 (which your config references), run:

  sudo pip2 install django [your-c-cpp-binding-library]
  

• To confirm the exact path of your system's native site-packages, run this command:

  python2 -c "import site; print(site.getsitepackages())"
  

  You'll get output like /usr/local/lib/python2.7/site-packages or /usr/lib/python2.7/dist-packages—save this path for your Apache config.

2. Update Your Apache Virtual Host Config #

Your current 000-default.conf includes a virtual environment path (myprojectenv), which we need to replace with your native Python's site-packages path. Here's the adjusted config:

<VirtualHost *:80>
    # Uncomment and set ServerName if you have a domain (e.g., ServerName www.example.com)

    Alias /static /home/jai/myproject/protocol/static
    <Directory /home/jai/myproject/protocol/static>
        Require all granted
    </Directory>

    <Directory /home/jai/myproject/pep_learn>
        <Files wsgi.py>
            Require all granted
        </Files>
    </Directory>

    # Replace the site-packages path with the one you found earlier
    WSGIDaemonProcess myproject python-path=/home/jai/myproject:/usr/local/lib/python2.7/site-packages
    WSGIProcessGroup myproject
    WSGIScriptAlias / /home/jai/myproject/pep_learn/wsgi.py

    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

Key changes:

• Removed the virtual environment path (/home/jai/myproject/myprojectenv/lib/python2.7/site-packages) from WSGIDaemonProcess
• Replaced it with your native Python's site-packages path (e.g., /usr/local/lib/python2.7/site-packages)

3. Fix File Permissions #

Apache runs as the www-data user by default, so you need to ensure it can access your project files and the C/C++ binding library:

• Grant read access to your project directory:

  sudo chmod -R 755 /home/jai/myproject
  

• If your C/C++ library has restricted permissions, update its directory too:

  sudo chmod -R 755 /usr/local/lib/python2.7/site-packages/[your-library-folder]
  

• Optional: Set the owner of your project files to www-data for full access (avoids most permission issues):

  sudo chown -R www-data:www-data /home/jai/myproject
  

4. Test the Setup #

• First, verify your native Python can load the binding library and Django:
  Create a test script (e.g., test_imports.py):

  import sys
  sys.path.insert(0, '/home/jai/myproject')
  try:
      import [your-c-cpp-library]
      print("C/C++ library loaded successfully")
      import django
      print(f"Django version: {django.get_version()}")
  except Exception as e:
      print(f"Error: {str(e)}")
  

  Run it with your native Python:

  python2 test_imports.py
  

  If this runs without errors, your environment is correctly set up.

• Restart Apache to apply config changes:

  sudo systemctl restart apache2
  

• If the app doesn't load, check Apache's error log for clues:

  tail -f /var/log/apache2/error.log
  

  Look for import errors—these usually mean either the path is wrong or permissions are missing.

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