Re: Cherokee for home developing

Thanks for all your answer, the topic get a little divergence, but
it's ok, I still use Cherokee for developing even if is not so
comfortable as I thought.

> The best way to save yourself time and effort is really to use the
> Django development server when testing out alterations.

Yes I guess so, but I had many problems to serve static files, and the
:8000 port wasn't so cool so I tried to work with a production web
server even for the developing.

> Karim, you may find that refreshing your project is easier with uWSGI as opposed to something
> like FastCGI, in reference to your question about having to restart Cherokee each time you make changes.

Yes, I noted that when I edit a url and sometimes the code, I have to
kill the fastcgi process to see the result in the browser. I think
that I could run the fastcgi as explained in the django documentation:

./manage.py runfcgi method=prefork socket=/home/user/mysite.sock
pidfile=django.pid

and map in vim file a kill command

kill `cat $PIDFILE`

Another solution is take a look at the uWSGI configuration

Anyway is a nice topic ;-)

--
K.
Blog Personale: http://www.karimblog.net

--
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 django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.