-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Despite all this, any URL below 127.0.0.1/test/ just returns the Welcome > page. It also doesn't throw errors when I enter non-existent URLs, even > though debug_info is enabled in Django.
Nevermind, I found the (my) mistake: I did not realize that the fcgi server process, once launched by Cherokee, exists independently. So when I change some Django code (e.g. URL patterns), I have to reload this process - which cannot be done by restarting cherokee. As it took me some while to figure out how to do this, here is my current solution: - - ps ax -> to find the pid of the python process which is in charge of the fcgi process - - kill -9 "pid-of-python-process" That's it, the fcgi process is restarted (with the changed code) the next time a request is made to a Django-governed URL. Two little questions remain: - - at the end of the Cherokee Danfo documentation (http://www.cherokee-project.com/doc/cookbook_django.html) there is an example for deploying "your Django application directly instead of through manage.py" - does this mean the fcgi reload will be automatically done when restarting Cherokee? And could someone explain the setup in more detail? - - the Django docs suggest adding "pidfile=django.pid" as a parameter when starting the fcgi server, so it is easier to kill (http://docs.djangoproject.com/en/dev/howto/deployment/fastcgi/#examples). When I add this parameter in the Cherokee admin information source, I get a 503 error for the URLs that are supposed to be handled by Django. What can be the reason for this? Saludos, Gregor -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpR1+sACgkQepJNjKMaIWUezwCeLvnCJWvuviTnxw3Razb1ADSq GmAAn1ov5Z0Zk9W2Jb6qDo8OknwvIuvy =X3+C -----END PGP SIGNATURE----- _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
