When I do this, I get a warning regarding the first one being on a given port and the second on the same port. When I atempt to go to my www.domain2.com I get what is what is at www.domain1.com

-- solution found --

I had to add a  NameVirtualHost directive (I placed it right after the listen directive)

NameVirtualHost *:<port>

where port is the port already in your listen directive.

Last edited by itgoesclick (2006-11-02 18:11:00)

Can you give a brief description of how you've got things set up on DreamHost?

IAIHMB wrote:

Can you give a brief description of how you've got things set up on DreamHost?

DreamHost is a completely different kettle of fish - using fcgi rather than mod_python.

I simply have each instance running under a separate user, so all the code lives in separate directories, and I can kill each user's python process individually. I simply point a different sub-domain at each Django instance and it all works - except not too fast, and lately the one instance that gets a bit of traffic keeps locking up.

David's solution works if you have each django instance running at separate directory within the same domain name. However I needed to have each instance running under its own subdomain. Fortunately Remi came up with the following, which works well:

Remi wrote:

Well, I did some testing and I think I got what you want working.
Here is what I did:

I created one django app with the control panel ($HOME/webapps/django)
I created 3 sub-directories (sub1, sub2 and sub3) and put a Django project (myproject) in each of them.
So I have the following files:

[test12@web4 django]$ pwd
/home2/test12/webapps/django
[test12@web4 django]$ ls -R
.:
apache2 sub1 sub2 sub3

./apache2:
bin conf logs modules

./apache2/bin:
httpd start stop

./apache2/conf:
httpd.conf mime.types

./apache2/logs:
access.log error.log httpd.pid

./apache2/modules:
libphp5.so mod_cgi.so mod_include.so mod_python.so
mod_access.so mod_dav_fs.so mod_info.so mod_rewrite.so
mod_actions.so mod_dav.so mod_ldap.so mod_setenvif.so
mod_alias.so mod_dav_svn.so mod_log_config.so mod_speling.so
mod_asis.so mod_deflate.so mod_log_forensic.so mod_ssl.so
mod_auth_anon.so mod_dir.so mod_logio.so mod_status.so
mod_auth_dbm.so mod_disk_cache.so mod_mem_cache.so mod_suexec.so
mod_auth_digest.so mod_env.so mod_mime_magic.so mod_unique_id.so
mod_auth_ldap.so mod_expires.so mod_mime.so mod_userdir.so
mod_auth.so mod_ext_filter.so mod_negotiation.so mod_usertrack.so
mod_authz_svn.so mod_fastcgi.so mod_proxy_connect.so mod_vhost_alias.so
mod_autoindex.so mod_file_cache.so mod_proxy_ftp.so
mod_cache.so mod_headers.so mod_proxy_http.so
mod_cern_meta.so mod_imap.so mod_proxy.so

./sub1:
myproject

./sub1/myproject:
__init__.py manage.py settings.pyc urls.pyc
__init__.pyc settings.py urls.py

./sub2:
myproject

./sub2/myproject:
__init__.py manage.py settings.pyc urls.pyc
__init__.pyc settings.py urls.py

./sub3:
myproject

./sub3/myproject:
__init__.py manage.py settings.py urls.py
[test12@web4 django]$


Then I created 3 subdomains (sub1|2|3.test12.webfactional.com) and mounted my django app on these subdomains with the control panel.

Then I used the following httpd.conf file:

Listen 127.0.0.1:2678
NameVirtualHost 127.0.0.1:2678
ServerRoot "/home2/test12/webapps/django/apache2"
LoadModule python_module /home2/test12/webapps/django/apache2/modules/mod_python.so
LoadModule log_config_module /home2/test12/webapps/django/apache2/modules/mod_log_config.so
LoadModule dir_module /home2/test12/webapps/django/apache2/modules/mod_dir.so
LoadModule mime_module /home2/test12/webapps/django/apache2/modules/mod_mime.so
LoadModule rewrite_module /home2/test12/webapps/django/apache2/modules/mod_rewrite.so
LoadModule env_module /home2/test12/webapps/django/apache2/modules/mod_env.so
User test12
Group test12
LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
CustomLog /home2/test12/webapps/django/apache2/logs/access.log combined
Errorlog /home2/test12/webapps/django/apache2/logs/error.log
ServerLimit 2
<VirtualHost 127.0.0.1:2678>
ServerName sub1.test12.webfactional.com
DocumentRoot /home2/test12/webapps/django/sub1/myproject
<Location "/">
SetHandler python-program
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE myproject.settings
PythonPath "['/home2/test12/webapps/django/sub1'] + sys.path"
PythonDebug On
</Location>
</VirtualHost>

<VirtualHost 127.0.0.1:2678>
ServerName sub2.test12.webfactional.com
DocumentRoot /home2/test12/webapps/django/sub2/myproject
<Location "/">
SetHandler python-program
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE myproject.settings
PythonPath "['/home2/test12/webapps/django/sub2'] + sys.path"
PythonDebug On
</Location>
</VirtualHost>

<VirtualHost 127.0.0.1:2678>
ServerName sub2.test12.webfactional.com
DocumentRoot /home2/test12/webapps/django/sub3/myproject
<Location "/">
SetHandler python-program
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE myproject.settings
PythonPath "['/home2/test12/webapps/django/sub3'] + sys.path"
PythonDebug On
</Location>
</VirtualHost>

So if you want to use this approach on your own account, just swap in your own domains names, directory names and port number. You can determine your port number by looking in your existing httpd.conf file (look for the line that starts with 'Listen').

The one oustanding issue is that I don't have a way of rebooting each instance separately. This means that each time I make a change to the development server I have to reboot all three instances - which is not really ideal.

I tried to set 'MaxRequestsPerChild 1' for the development server only, so that I don't have to restart apache to see changes. (This is recommended by the Django folks at http://www.djangoproject.com/documentat … mod-python). But unfortunately I can't put this directive anywhere inside the <VirtualHost> section, hence I can only set it for all 3 sites, or none.

As an alternative approach, I tried putting 'PythonAutoReload On' inside the <Location "/"> block, but this did not produce the desired effect. I'm not sure why, although a quick Google search indicated that this directive has been buggy in some recent versions of mod_python. In any case I'm convinced that it's meant to do what I want.

I guess my best option might be to do development off-line, but then I lose the luxury of developing with a well-populated database. If there were some way I could  install Django elsewhere, but connect to my database on WebFaction I could get around this, but I don't think external access to databases is possible with WebFaction. Does anyone know if there is a way to do this?

It also occurs to me that I could bypass Apache and mod_python for the development server, and use the built-in Django development server, but I don't have any idea how to configure the IP address and port number so that I can access it remotely. It also seems quite likely that this wouldn't work at all in a shared hosting environment.

Thomas

I guess my best option might be to do development off-line, but then I lose the luxury of developing with a well-populated database. If there were some way I could  install Django elsewhere, but connect to my database on WebFaction I could get around this, but I don't think external access to databases is possible with WebFaction. Does anyone know if there is a way to do this?

I'm surprised that you don't develop locally, I find it more productive especially when debugging. Since you're using Subversion to manage your project that would make things really easy. You could even take things a step further and add Capistrano to the mix. You never mentioned what database you were using, but I just tried using MySQL's GRANT and it's off limits. If SQLite is an option it's something that you might want to consider, since SQLite databases consist of a flat file you could keep it under version control.

Last edited by IAIHMB (2006-11-23 22:02:00)

Ok, how about this possibility?

I have one project/application that I want to run on three different urls (subdomain1.domain1.com, subdomain2.domain1.com, domain2.com) with three different sets of data.  I'm using Django's site framework so I've set up three domains in the admin section and I've created three settings files each with a different SITE_ID and I've set up my http.conf file similar to what is in the first post of this thread.  Now I'm running all three domains off of one website as defined in the Webfaction control panel. 
When I visit the urls, only the first one works while the other two do not (I'm getting a Django error which I don't understand)

Am I close with this setup?  Do I need to set up a discreet Website for each domain in Webfaction's control panel?  Do I need to change some other setting?  Possibly give each site its own URL conf?

Any ideas?

Thanks,
Condredge

landslideinc wrote:

Ok, I've tried adding another site for one of my domains, but I'm still getting the same error, so that's ruled out. Any ideas?

Are you sharing the same files for your 3 Django sites ? Maybe you should copy the project files three times ?

Remi.

I'm running basically the same setup as tttallis outlines above, but I only have two VirtualHosts. Everything works fine except that when Django uses its APPEND_SLASH setting to add slashes the port number gets appended to the base url... in other words a request for http://mysite.com/photos becomes http://mysite.com:2694/photos/

Can anyone explain why that's happening and how I can fix it?

skam wrote:

luxagraf wrote:

I'm running basically the same setup as tttallis outlines above, but I only have two VirtualHosts. Everything works fine except that when Django uses its APPEND_SLASH setting to add slashes the port number gets appended to the base url... in other words a request for http://mysite.com/photos becomes http://mysite.com:2694/photos/

Can anyone explain why that's happening and how I can fix it?

I've got the same problem, and APPEND_SLASH is set to False in my settings.py
I think that it not depends on Django, PREPEND_WWW = True works correctly without adding the port number in the base url.

The problem persists also if I remove 'django.middleware.common.CommonMiddleware' from MIDDLEWARE_CLASSES

skam wrote:

luxagraf wrote:

I'm running basically the same setup as tttallis outlines above, but I only have two VirtualHosts. Everything works fine except that when Django uses its APPEND_SLASH setting to add slashes the port number gets appended to the base url... in other words a request for http://mysite.com/photos becomes http://mysite.com:2694/photos/

Can anyone explain why that's happening and how I can fix it?

I've got the same problem, and APPEND_SLASH is set to False in my settings.py
I think that it not depends on Django, PREPEND_WWW = True works correctly without adding the port number in the base url.

If anyone is still having that problem, the trailing slash is added by apache (the request doesn't even make it to Django). This behavior is caused by the "mod_dir" module, so if you remove the "LoadModule dir_module ..." and the "DirectoryIndex ..." lines from your apache config the problem will go away.

Note that our Django installer was fixed a while ago so new Django apps don't load "mod_dir" in the apache config anymore.

Cheers,

Remi.

Do you mean that you'd like the shared/ directory to be in your PYTHONPATH? If so, add it to your PYTHONPATH lines:

PythonPath "['/home/example/webapps/django/', 'XXX/shared/'] + sys.path"

If that's not what you mean then you're going to have to explain the desired affect in a little more detail.

Hope it helps.

This is going poorly. If I use IAIHMB's example, I can't import my settings:
    raise ImportError, "Could not import settings '%s' (Is it on sys.path? Does it have syntax errors?): %s" % (self.SETTINGS_MODULE, e)

If I use Remi's example, I get a DJANGO_SETTINGS_MODULE not set error.