Yes. I finally did get it to work. But my issues weren't database 
related. Turned out to be something fairly simple with .htaccess as I 
suspected. (I'm not even up to the point of database access yet. And 
I'll be using PostgreSQL as that's what I know.)

Michael



Ralf wrote:
> Did you get your Django site to work? What database are you using?
> 
> I'm also trying to get Django to work on hostmonster.com, but I'm
> having trouble with the MySQL backend, it doesn't seem to be
> installed.
> 
> I tried manually installing it (copying files), but I get this error:
> 
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: File "/home/
> tourista/python/flup/server/fcgi_base.py", line 558, in run
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: protocolStatus,
> appStatus = self.server.handler(self)
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: File "/home/
> tourista/python/flup/server/fcgi_base.py", line 1116, in handler
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: result =
> self.application(environ, start_response)
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: File "/home/
> tourista/python/django/core/handlers/wsgi.py", line 184, in __call__
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr:
> self.load_middleware()
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: File "/home/
> tourista/python/django/core/handlers/base.py", line 29, in
> load_middleware
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: mod =
> __import__(mw_module, {}, {}, [''])
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: File "/home/
> tourista/python/django/contrib/sessions/middleware.py", line 2, in ?
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: from
> django.contrib.sessions.models import Session
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: File "/home/
> tourista/python/django/contrib/sessions/models.py", line 3, in ?
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: from django.db
> import models
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: File "/home/
> tourista/python/django/db/__init__.py", line 11, in ?
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: backend =
> __import__('django.db.backends.%s.base' % settings.DATABASE_ENGINE,
> {}, {}, [''])
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: File "/home/
> tourista/python/django/db/backends/mysql/base.py", line 12, in ?
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr: raise
> ImproperlyConfigured, "Error loading MySQLdb module: %s" % e
> [Mon Jan 14 03:17:20 2008] [warn] mod_fcgid: stderr:
> ImproperlyConfigured: Error loading MySQLdb module: /home/tourista/
> python/_mysql.so: cannot open shared object file: No such file or
> director
> 
> I guess I'll need to recompile from source on the server, but I don't
> have ssh access yet.
> 
> Ralf
> 
> 
> On Jan 8, 8:32 am, Michael Hipp <[EMAIL PROTECTED]> wrote:
>> Michael Hipp wrote:
>>> Hello,
>>> I'm hoping to rework my website into Django, but am having trouble at my
>>> shared hosting provider (HostMonster).
>>> They don't support mod_python, so Hostmonster said to add this to .htaccess
>>> for FastCGI:
>>>    AddHandler fcgid-script .fcgi
>>> I did that and my html sites still work, but when I add the recommendations
>>> from Django my html sites don't work and neither does my fledgling Django 
>>> site.
>>>    AddHandler fastcgi-script .fcgi
>>>    RewriteEngine On
>>>    RewriteCond %{REQUEST_FILENAME} !-f
>>>    RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]
>>> I also did the mysite.fcgi file. My Django site just returns blank pages. 
>>> The
>>> html sites get an 'Internal Server Error'.
>> Thanks to help from this list the Django site is now funcitonal. But the
>>   old html sites still return Internal Server Errors.  Here's what in
>> the logs:
>>
>> [Mon Jan 07 23:28:15 2008] [error] [client 75.116.4.1] Request exceeded
>> the limit of 10 internal redirects due to probable configuration error.
>> Use 'LimitInternalRecursion' to increase the limit if necessary. Use
>> 'LogLevel debug' to get a backtrace.
>>
>> I assume this is a function of the .htaccess file. How do I get it to
>> route around django for the html sites?
>>
>> Thanks,
>> Michael
> > 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to