I don't think that's stupid. Some of our wizards prepende 'python' to the interpreter line, just for safety. I've also seen a lot of Python scripts not beginning with the usual '#!/usr/bin/env python' (instead they call a python binary on a not_so_portable path). If Oli is using different platforms maybe this could be the issue.
Antonio Pérez wrote: > Hello, > > On Thu, Oct 8, 2009 at 5:33 PM, Oli Warner <[email protected]> wrote: > > >> I've got a django information source that just refuses to load via Cherokee. >> It loads fine if I type the exact command into the terminal (and pages are >> accessible through Cherokee if it's running). It's very odd. >> >> Connection: /websites/mysite-co-uk/sock >> Interpreter: /websites/mysite-co-uk/manage.py runfcgi >> workdir=/websites/mysite-co-uk/ maxspare=3 method=threaded protocol=scgi >> socket=sock pidfile=pid >> >> The server is running as the same user I log in as. I'm using similar >> commands for other django websites (just changing the paths). Any idea's why >> it's not launching? >> > > Mmmmm... Maybe I'm saying something stupid but... are you sure that > "manage.py" has the executable bit set? > -- [email protected] http://unixwars.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
