For example, if you are using uWSGI 0.9.2.6 you can use an XML document similar
to this:
/srv/python-environments/voxinfinitus/
/srv/python-environments/
DJANGO_SETTINGS_MODULE=voxinfinitus.settings
django.core.handlers.wsgi:WSGIHandler()
6
/tmp/cherokee/voxi-live.so
On Mon, Nov 1, 2010 at 21:21, Max Countryman wrote:
> Karim, I would set it up using a UNIX socket. Then all you have to do is rm
> the socket path. :) There is no need to kill uWSGI in that case.
Let me study that, because there is always a newbie side in me that
sometimes scream out :D
If this
Karim, I would set it up using a UNIX socket. Then all you have to do is rm the
socket path. :) There is no need to kill uWSGI in that case.
On Nov 1, 2010, at 3:13 PM, Karim Gorjux wrote:
> On Sun, Oct 31, 2010 at 01:27, Max Countryman wrote:
>> Yes, absolutely. :D Good luck!
>
> Max, I'm try
On Sun, Oct 31, 2010 at 01:27, Max Countryman wrote:
> Yes, absolutely. :D Good luck!
Max, I'm trying with uwsgi and Cherokee. Seems to work, but if I edit
the code, I have to kill the uwsgi process to see the modification on
the browser. Is that normal?
--
K.
Blog Personale: http://www.karimbl
Yes, absolutely. :D Good luck!
On Oct 30, 2010, at 5:04 PM, Karim Gorjux wrote:
> 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:
>
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
This may be of use to anyone using any version of Cherokee prior to 1.09:
http://lists.octality.com/pipermail/cherokee/2010-September/013432.html
There are several threads that detail the manual set up process. But the key
here is that the wizard is, as Roberto states, "(currently) totally broke
Karim,
If you hve not already quit reading these posts(I wouldnt blame you if
you had) I want to once again apologise.
I only posted as I was glad to see someone else using Cherokee and
wished to offer a small insight into another way of serving python
code.
The whole thing has become idiotic a
"Anyway, my intent here was to help. It's ridiculous how everything
has to be reduced to pedantic argumentation and sanctimonious advice
about what to post where."
I was trying to be courtesy towards Karim as this is his post.
Consider, Max, whether this post would have been better had you not
co
Generally, yes.
If you're using a socket, you can rm the socket path each time you update. That
will avoid the need to restart Cherokee.
On Oct 29, 2010, at 4:31 AM, Karim Gorjux wrote:
> I have just one question. While I'm editing the source of the project,
> to see the result I have always to
Rob,
I don't want to email you directly. I'm sure you're a nice guy and everything,
but I'm on this list to contribute to the list. Please stop asking this. That
*is* obnoxious.
I'm sorry you see my comments as unhelpful or "unconstructive[sic]", however
please remember you are not the only o
On Oct 29, 2010, at 5:45 AM, Robbington wrote:
> Actually I mentioned Uwsgi,
You missed where I referenced, where was here:
On Oct 28, 2010, at 2:27 PM, Karim Gorjux wrote:
> Now I solved all my problems working with settings.py. Seems that also
> the debug works, but If I'll be again in troub
Dear Paul and Max,
As I mentioned before please email me directly should you wish to
continue this discussion further, and or create a new post. I feel it
unfair to discuss this in this particular forum as it is unrelated to
the original subject matter.
I meant no offense to Max, I can see how th
Dear Rob,
Am Freitag, den 29.10.2010, 02:45 -0700 schrieb Robbington:
[…]
> Actually I mentioned Uwsgi,
>
> Perhaps if you are going to state potential bugs with software you
> could be so kind as to add the specifics in your posts and not just
> ambiguous statements such as "Do not use the uw
Hey Karim,
The best way to save yourself time and effort is really to use the
Django development server when testing out alterations.
Max,
Actually I mentioned Uwsgi,
Perhaps if you are going to state potential bugs with software you
could be so kind as to add the specifics in your posts and n
I have just one question. While I'm editing the source of the project,
to see the result I have always to restart the server or there is
another way?
--
K.
Blog Personale: http://www.karimblog.net
--
You received this message because you are subscribed to the Google Groups
"Django users" group
He mentioned uwsgi. He should know that the wizard is currently broken. That
means that it produces a configuration that doesn't work properly. Please refer
to the Cherokee mailing list of you're unaware of these issues. It should be
fixed in v1.09 which is coming soon. Thanks!
On Oct 28, 2010,
I use Django + UWSGI + Cherokee with all my sites , with around 200k page
views a day.
Various teething problems, but generally stable.
On Thu, Oct 28, 2010 at 7:32 PM, Max Countryman wrote:
> Oh I forgot to mention! Do not use the uwsgi wizard: it's currently broken.
> Expect a fix soon and re
Hi Max,
I am not sure what you mean by ' Do not use the uwsgi wizard: it's
currently broken'?
Rob,
Ps, should you wish to discuss this further, perhaps it is better you
email me directly, as to avoid filling Karims post with unnecessary
messages.
--
You received this message because you are s
Oh I forgot to mention! Do not use the uwsgi wizard: it's currently broken.
Expect a fix soon and refer to the various threads detailing the set up process
without the wizard on Cherokee's mailing list.
On Oct 28, 2010, at 14:06, Robbington wrote:
> Glad to finally see some one using Cherokee
Rob,
I have been using Cherokee for Django deployment for almost a year now. I know
several other devs who prefer it as well. Also there's always some activity on
the Cherokee list itself related to Django.
On Oct 28, 2010, at 14:06, Robbington wrote:
> Glad to finally see some one using Ch
On Thu, Oct 28, 2010 at 21:06, Robbington wrote:
> Glad to finally see some one using Cherokee with django. Dont just use
> it in development, its actually less memory intensive than apache as
> well as having an awesome admin interface.
Now I can just develop on Django with Cherokee I haven't an
Glad to finally see some one using Cherokee with django. Dont just use
it in development, its actually less memory intensive than apache as
well as having an awesome admin interface.
Anyway enough plugging.
To avoid problems and for simplicty I would advise using Cherokee
Uwsgi config to serve up
On Thu, Oct 28, 2010 at 19:32, Karim Gorjux wrote:
> Hi all! I'm trying to create my devbox for Django and I use a server
I fixed the problem with the settings.py and now admin works.
The problem now is to avoid the flup's "Unhandled Exception" and let
django shows it debug
--
K.
Blog Personal
Hi all! I'm trying to create my devbox for Django and I use a server
in my lan with Ubuntu and Cherokee installed in. For every project I
use virtualenv so I install django and flup and I create in cherokee
panel the virtual server using the path of my virtualenv. All I do is
explained in the Chero
25 matches
Mail list logo
