PROSAGA码农传奇-模型托管-apache和mod

我想举办它使用Debian的5同一服务器下的几个场所，说我有site1，site2和site3，并承担我的IP是155.55.55.1：
<pre><code>site1: 155.55.55.1:80 , script at /opt/django/site1/
site2: 155.55.55.1:8080, script at /opt/django/site2/
site3: 155.55.55.1:8090, script at /opt/django/site3/
</code></pre>这是我的默认Apache：
<pre><code><VirtualHost *:80>
 ServerName /
 ServerAlias */
 DocumentRoot /opt/django/site1/
 LogLevel warn
 WSGIScriptAlias / /opt/django/site1/apache/django.wsgi
 Alias /media /opt/django/site1/media/statics
 Alias /admin_media /home/myuser/Django-1.1/django/contrib/admin/media 
</VirtualHost>

<VirtualHost *:80>
 DocumentRoot "/usr/share/phpmyadmin"
 ServerName /phpmyadmin
 Alias /phpmyadmin /usr/share/phpmyadmin
 <Directory /usr/share/phpmyadmin>
 Options Indexes FollowSymLinks
 AllowOverride None
 Order Deny,Allow
 Allow from all
 </Directory>
</VirtualHost>
</code></pre>这是我的wsgi配置site1，位于/opt/django/site1/apache/django.wsgi：
<pre><code>import os, sys
import django.core.handlers.wsgi

sys.path.append('/opt/django')
sys.path.append('/opt/django/site1')

os.environ['DJANGO_SETTINGS_MODULE'] = 'site1.settings'
application = django.core.handlers.wsgi.WSGIHandler()
</code></pre>我如何添加site2和site3，它们是基于Django的站点，将像一样提供服务site1？

您的ServerName / ServerAlias指令错误。ServerName应该是主机名。您可能应该删除ServerAlias。

然后只需执行明显且重复的VirtualHost / Listen指令，只需更改文件系统中脚本的端口号和位置即可。

最后，不要将DocumentRoot设置为您的Django代码所在的位置，因为如果您填充Apache配置，它很容易意外地暴露您的源代码以供下载。因此，只需从VirtualHost for Django网站删除DocumentRoot指令即可。

```
Listen 80

<VirtualHost *:80>
ServerName www.example.com
WSGIScriptAlias / /opt/django/site1/apache/django.wsgi
Alias /media /opt/django/site1/media/statics
Alias /admin_media /home/myuser/Django-1.1/django/contrib/admin/media

<Directory opt/django/site1/apache>
Order allow,deny
Allow from all
</Directory>

<Directory /home/myuser/Django-1.1/django/contrib/admin/media>
Order allow,deny
Allow from all
</Directory>
</VirtualHost>

Listen 8080

<VirtualHost *:8080>
ServerName www.example.com
WSGIScriptAlias / /opt/django/site2/apache/django.wsgi
Alias /media /opt/django/site2/media/statics
Alias /admin_media /home/myuser/Django-1.1/django/contrib/admin/media

<Directory opt/django/site2/apache>
Order allow,deny
Allow from all
</Directory>

<Directory /home/myuser/Django-1.1/django/contrib/admin/media>
Order allow,deny
Allow from all
</Directory>
</VirtualHost>

Listen 8090

<VirtualHost *:8090>
ServerName www.example.com
WSGIScriptAlias / /opt/django/site3/apache/django.wsgi
Alias /media /opt/django/site3/media/statics
Alias /admin_media /home/myuser/Django-1.1/django/contrib/admin/media

<Directory opt/django/site3/apache>
Order allow,deny
Allow from all
</Directory>

<Directory /home/myuser/Django-1.1/django/contrib/admin/media>
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
```

我还添加了缺少的Directory指令，以允许访问静态文件。但是，您应该查看路径。

确保您阅读：

http://code.google.com/p/modwsgi/wiki/IntegrationWithDjango http://code.google.com/p/modwsgi/wiki/ConfigurationGuidelines#Hosting_Of_Static_Files

了解更多信息。

更新1

顺便说一句，由于您在同一Apache中使用PHP，因此最好使用mod_wsgi守护程序模式并将每个Django实例推入其自己的单独进程中。即使由于PHP而将主要的Apache进程强制为单线程，也可以使这些进程成为多线程。与使用prefork MPM在嵌入式模式下在每个进程中运行多个Django实例相比，最终结果将使用更少的内存。您的Django代码只需要是线程安全的即可。除上述配置外，还需要向每个Django VirtualHost添加WSGIDaemonProcess / WSGIProcessGroup，其中，每个VirtualHost的守护进程组的名称均不同。

```
<VirtualHost *:80>
WSGIDaemonProcess site1 display-name=%{GROUP}
WSGIProcessGroup site1
... existing stuff
</VirtualHost>

<VirtualHost *:8080>
WSGIDaemonProcess site2 display-name=%{GROUP}
WSGIProcessGroup site2
... existing stuff
</VirtualHost>

<VirtualHost *:8090>
WSGIDaemonProcess site3 display-name=%{GROUP}
WSGIProcessGroup site3
... existing stuff
</VirtualHost>
```

这也使您可以更轻松地重新启动每个Django实例，而无需重新启动整个Apache。读：

http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide#Delegation_To_Daemon_Process http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode

apache和mod_wsgi的多个django网站