Hi, Wishi,
1. Make sure that django fcgi process is running at all.
$ ps ax | grep manage
2. Lighttpd config looks a bit weird for me. Why to have two fcgi processes
- one for admin and other for regular site?
Mine looks like this:
===
fastcgi.server = (
"/django.fcgi" => (
"djangolocal" => (
"socket" => "/tmp/django.sock",
"check-local" => "disable",
)
)
)
alias.url = (
"/static/" => "/path/to/your/projects/media/files/",
"/media/" => "/path/to/django/contrib/admin/media/",
)
# rewrites for django
url.rewrite-once = (
"^(/media.*)$" => "$1",
"^(/static.*)$" => "$1",
"^/favicon\.ico$" => "/media/favicon.ico",
"^(/.*)$" => "/django.fcgi$1"
)
===
Why use TCP for communicating to django fcgi daemon? I suppose that using
unix socket should be significantly faster. To start up django fcgi daemon
use command like this:
$ python ./manage.py runfcgi method=prefork socket=/tmp/django.sock
pidfile=/tmp/django.pid
Note that I have set MEDIA_URL to '/static/' in project's settings.py file
to point to site media.
Another suggestion: If you are just getting acknowledged with Django it
would be more useful to begin with Django 1.0 as it promises future
consistency of API's.
Best regards,
Valts.
On Thu, Sep 11, 2008 at 12:14 AM, wishi <[EMAIL PROTECTED]> wrote:
>
> Hi!
>
>
> Thanks for the tip. Nevertheless: I don't know what's the meaning of
> this either:
>
>
> 2008-09-10 21:52:34: (mod_fastcgi.c.2721) establishing connection
> failed: Connection refused socket: tcp:127.0.0.1:9090
> 2008-09-10 21:52:40: (mod_fastcgi.c.2667) fcgi-server re-enabled:
> tcp:127.0.0.1:9090
>
>
> - Because at 9090 locally there's the django fcgi, which doesn't seem to
> run.
> What would be very helpful: a howto or another config-file of lighttpd I
> could use to diff through.
>
> Just the startup-problems I guess, sorry.
>
>
> wishi
>
>
>
> Valts Mazurs schrieb:
> > Hi,
> >
> > Take a look at lighttpd's error log (see server.errorlog setting in
> lighttpd
> > config file for exact error log location)
> >
> > Valts.
> >
> > On Wed, Sep 10, 2008 at 10:49 PM, wishi <[EMAIL PROTECTED]> wrote:
> >
> >> i mates ;)
> >>
> >> These days I thought working myself into Django - to get some new
> >> skills. I could need some start-up help to configure my environment,
> >> which isn't the "Apatschi" with mod_python. I'm using a lighttpd in my
> >> Debian server environment, that's going to be configured:
> >>
> >> Therefore I added mod_rewrite and mod_fastcgi as described in this
> >> Howto documentation here:
> >> http://sam.bluwiki.com/blog/labels/linux.php
> >>
> >> server.modules = (
> >> "mod_access",
> >> "mod_alias",
> >> "mod_rewrite",
> >> "mod_fastcgi",
> >> "mod_accesslog",
> >> "mod_redirect",
> >> "mod_status",
> >> # "mod_evhost",
> >> "mod_compress",
> >> "mod_usertrack",
> >> # "mod_rrdtool",
> >> # "mod_webdav",
> >> [...]
> >>
> >> I configured the fastcgi stuff:
> >>
> >> fastcgi.server = (
> >> ".php" => ((
> >> "bin-path" => "/usr/bin/php5-cgi",
> >> "socket" => "/tmp/php.socket"
> >> )),
> >> "django.fcgi" => (
> >> "main" => (
> >> "host" => "127.0.0.1",
> >> "port" => 9090, #set the port numbers to what-eva you
> >> want
> >> ),
> >> ),
> >> "admin.fcgi" => (
> >> "admin" =>
> >> (
> >> "host" => "127.0.0.1", "port" => 9091, )
> >> )
> >> )
> >>
> >> And the rewrite stuff:
> >>
> >> url.rewrite-once = (
> >> "^(/media.*)$" => "$1",
> >> "^(/static.*)$" => "$1",
> >> "^/favicon\.ico$" => "/media/favicon.ico",
> >> "^(/admin/.*)$" => "/admin.fcgi$1", "^(/.*)$" => "/django.fcgi
> >> $1"
> >> )
> >>
> >>
> >> And sweet as, that's it. Django is working... was just apt-get install
> >> blabla.
> >>
> >> % django-admin --version
> >> 0.95.1
> >>
> >>
> >> % ls /var/django/testproject
> >> __init__.py manage.py settings.py urls.py
> >>
> >> No modifications jet, the basic django-test-webserver works fine.
> >>
> >> % python manage.py runfcgi method=prefork host=127.0.0.1 port=9090
> >> pidfile=django.pid
> >> [no error]
> >>
> >>
> >> Nevertheless - the httpd starts without any error, and django-admin
> >> works, too - I get an internal server error 500. Does anybody know
> >> what's wrong or which steps may be needed for further debugging? Could
> >> be very helpful. The general documentation stuff focuses on Apache,
> >> which I completely dislike and don't want to have on my system.
> >>
> >> Thanks for help,
> >> Marius
> >>
> >>
> >> p.s.: I hope this message isn't on the list twice. Got some issues...
> >>
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
