Fixing Django Deployment with Apache and mod_wsgi

I can see several issues with your current setup that are likely causing the ModuleNotFoundError: No module named 'web' error.

The Python Path Issue

The main problem is with your python-path setting in the WSGIDaemonProcess directive. The Python path needs to include the directory containing your Django project, not just the virtual environment's bin directory.

Here are the key fixes needed:

1. Fix the Python Path in Apache Configuration

Change this line:

WSGIDaemonProcess example.com processes=2 threads=15 user=django_user group=www-data socket-user=#1001 python-path=/var/www/sites/example.com/env/bin python-home=/var/www/sites/example.com/env

To:

WSGIDaemonProcess example.com processes=2 threads=15 user=django_user group=www-data socket-user=#1001 python-path=/var/www/sites/example.com python-home=/var/www/sites/example.com/env

The python-path should point to the parent directory that contains your Django project, not to the virtual environment's bin directory.

2. Add Directory Configuration for the WSGI Script

Add this to your Apache configuration:

<Directory /var/www/sites/example.com/web/web>
    <Files wsgi.py>
        Require all granted
    </Files>
</Directory>

3. Ensure the wsgi.py File Uses the Correct Settings Module

Check your wsgi.py file and make sure it has the correct settings module. Based on your directory structure, it should contain:

PYTHONCopied
import os
from django.core.wsgi import get_wsgi_application

os.environ["DJANGO_SETTINGS_MODULE"] = "web.settings"  # Not setdefault

application = get_wsgi_application()

Note the use of os.environ["DJANGO_SETTINGS_MODULE"] instead of setdefault() as mentioned in the documentation to avoid issues when running multiple Django sites.

About the Nested Directory Structure

Yes, django-admin startproject web creates a nested directory structure by design:

• The outer web directory is a container for your project
• The inner web directory is the actual Python package for your project

This is the standard Django project layout and is expected. The nested structure helps separate your project's code from other files like manage.py.

Additional Troubleshooting Tips

1. Make sure Django is installed in your virtual environment:

   source /var/www/sites/example.com/env/bin/activate
   pip install django
   

2. Check permissions:

   chown -R django_user:www-data /var/www/sites/example.com
   chmod -R 755 /var/www/sites/example.com
   

3. Restart Apache after making changes:

   sudo systemctl restart apache2
   

4. Check Apache error logs for more detailed error messages:

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

These changes should resolve your issue with the "No module named 'web'" error by ensuring that the Python path is correctly set to find your Django project modules.