be great. If
> not, any pointers to where I can read more about lighty's use of URLs
> and Django's use of URLs would help.
>
> Thanks,
> Lisa
>
> On Aug 18, 12:55 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
> wrote:
>
> > On Mon, 2008-08-18 at 16:47
This problem still exists with django-1.0.
I've been researching a bit:
http://code.djangoproject.com/changeset/7297
does some changes. It works if I comment out the os.dup2 lines, but
that may not be very robust. I'm using threaded model, not fork.
On 12 ago, 18:51, Brian Victor <[EMAIL PROTEC
On Tue, Sep 16, 2008 at 10:25 AM, Wim Feijen <[EMAIL PROTECTED]> wrote:
>
> Hi Anders,
>
> For me, removing the slash in the FORCE_SCRIPT_NAME seemed to work. I
> am not using the admin interface, so I can't check on that.
>
> So I added to settings.py:
>
> FORCE_SCRIPT_NAME=""
>
> I totally agree
Hello Wim Feijen!
On Tue, 16 Sep 2008 01:25:58 -0700 (PDT) you wrote:
>
> Hi Anders,
>
> For me, removing the slash in the FORCE_SCRIPT_NAME seemed to work. I
> am not using the admin interface, so I can't check on that.
>
> So I added to settings.py:
>
> FORCE_SCRIPT_NAME=""
>
> I totally a
Hi Anders,
For me, removing the slash in the FORCE_SCRIPT_NAME seemed to work. I
am not using the admin interface, so I can't check on that.
So I added to settings.py:
FORCE_SCRIPT_NAME=""
I totally agree that this change with great consequences for all
lighttpd users is poorly documented.
Be
nters to where I can read more about lighty's use of URLs
and Django's use of URLs would help.
Thanks,
Lisa
On Aug 18, 12:55 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Mon, 2008-08-18 at 16:47 -0300, Gonzalo Almeida wrote:
> > hello,
> > I have a proble
On Sat, Sep 13, 2008 at 4:23 AM, Ramiro Morales <[EMAIL PROTECTED]> wrote:
> Have you tried what's suggested in
>
> http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#ChangedthewayURLpathsaredetermined
>
> (under the "lighttpd + fastcgi (and others)
On Sat, Sep 13, 2008 at 4:23 AM, Ramiro Morales <[EMAIL PROTECTED]> wrote:
> Have you tried what's suggested in
>
> http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#ChangedthewayURLpathsaredetermined
>
> (under the "lighttpd + fastcgi (and others)&
On Fri, Sep 12, 2008 at 9:33 PM, Anders Bergh <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm trying to host a Django 1.0 project on lighttpd 1.4.19 on Linux,
> following the lighttpd FastCGI in the Django documentation. However,
> it doesn't work, it seems to r
Hi,
I'm trying to host a Django 1.0 project on lighttpd 1.4.19 on Linux,
following the lighttpd FastCGI in the Django documentation. However,
it doesn't work, it seems to redirect to /mysite.fcgi for almost
anything I do.
Here's the config:
$HTTP["host"
wow that was easy,
thanks you very much malcolm
Gon
--
Linux user #466939
--~--~-~--~~~---~--~~
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
On Mon, 2008-08-18 at 16:47 -0300, Gonzalo Almeida wrote:
> hello,
> I have a problem with lighttpd + fastcgi,
> I used have the newforms-admin branch and everything worked fine.
> but when I started using the trunk version, the problems appeared.
> when I access http://localhos
hello,
I have a problem with lighttpd + fastcgi,
I used have the newforms-admin branch and everything worked fine.
but when I started using the trunk version, the problems appeared.
when I access http://localhost/admin/, I try to loggin in the admin.
and it redirect me to http://localhost
Panos Laganakos wrote:
This post[1] seems to have the same issue. Ticket 6063, which was
fixed at rev.6895.
Problem is that the whole project is written for 0.96.1. Any way this
can be fixed in 0.96.1?
My guess is that you'd have to backport the patch yourself.
This is one of the reasons th
This post[1] seems to have the same issue. Ticket 6063, which was
fixed at rev.6895.
Problem is that the whole project is written for 0.96.1. Any way this
can be fixed in 0.96.1?
[1]
http://groups.google.com/group/django-users/browse_thread/thread/f5c9a05970343c0a/7455719663bebf05?lnk=gst&q=fas
This is the lighty setup:
$HTTP["host"] == "manishop.solhost.org" {
var.serverpath = "/panos/manishop.solhost.org"
server.document-root = basedir + serverpath + "/manigifts/static"
server.errorlog = basedir + serverpath + "/logs/server.log"
accesslog.filename = basedir +
Hi Rajesh,
Thanks.
This was a dumb-dumb mistake I did.
I think I never realized that I was using the wrong port. (
My mind turned a blind spot to this :)
The whole lighttpd setup is working smoothly.
Thanks,
Venkat
On Apr 10, 11:41 pm, Rajesh Dhawan <[EMAIL PROTECTED]> wrote:
> Hi Venkat,
Hi Venkat,
>
> My fastcgi config is (added at the end of conf file),
> fastcgi.debug = 1
> fastcgi.server = (
> "/django.fcgi" => (
> "main" => (
> "host" => "127.0.0.1",
> "port" => 3456,
> )
>
> When I request the home page like,
> links 'http://127.0
;
>
>
> annacoder <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> > I am trying hard to figure out why my lighttpd + fastcgi + django
> > setup is not working.
> > First, I have verified my django project is OK by running it with the
> > local web server p
On Thu, 10 Apr 2008 06:06:16 -0700 (PDT)
annacoder <[EMAIL PROTECTED]> wrote:
>
> Hi,
> I am trying hard to figure out why my lighttpd + fastcgi + django
> setup is not working.
> First, I have verified my django project is OK by running it with the
> local web s
Hi,
I am trying hard to figure out why my lighttpd + fastcgi + django
setup is not working.
First, I have verified my django project is OK by running it with the
local web server provided by django.
To setup lighttpd, I followed the setup instructions from here:
http://wiki.slicehost.com
Karen,
The ticket says, "If flatpages and DEBUG=False and 404.html doesn't
exist it throws the error".
I have DEBUG=True, and I'm getting an "Unhandled Exception" error, not
the default yellow "Django 404 Error with DEBUG=True"
Anyways, the issue now seems to be with the way flatpages handles
5
On 12/5/07, Derek Payton <[EMAIL PROTECTED]> wrote:
>
>
> Apparently there was an issue with my svn. I downgraded to a previous
> revision (pre-6778), then back to trunk. Everything is working now,
> except flatpages. Here's the error from lighttpd's log:
> http://dpaste.com/26918/
>
> As per the l
Apparently there was an issue with my svn. I downgraded to a previous
revision (pre-6778), then back to trunk. Everything is working now,
except flatpages. Here's the error from lighttpd's log: http://dpaste.com/26918/
As per the last line in the log, I created a (blank) 404.html in my
templates
Derek just noticed in IRC that [6895] is still failing on flatpages.
--~--~-~--~~~---~--~~
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 unsubscr
Chris,
[EMAIL PROTECTED]:~/django-trunk$ svn update
At revision 6897.
Any ideas?
Thank you,
--Derek
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-
Sounds like this bug - http://code.djangoproject.com/ticket/6063
which was supposed to be fixed in [6895]. Are you sure you have the most
recent checkout?
-Chris
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Dja
Hello,
I was recently charged with installing a new development server at
work, and I'm having some trouble getting Django to work as FastCGI
under Lighttpd. The new server is setup identical to the old server,
except for some hardware upgrades and we moved from Ubuntu Dapper to
Ubuntu Gutsy.
Li
28 matches
Mail list logo
