If I have Django running with a wsgi adapter, and I execute a
manage.py command, will it spawn a new instance of Django just to
execute the command, or will it use an existing running instance?
I need to make a decision on writing a command that will be hit pretty
frequently by a node.js applicati
40 pm, Matt Robenolt wrote:
> If I have Django running with a wsgi adapter, and I execute a
> manage.py command, will it spawn a new instance of Django just to
> execute the command, or will it use an existing running instance?
>
> I need to make a decision on writing a command tha
You set up a 'media.aplikacje' alias in your nginx config, but your
media is still attempting to be pulled from 'aplikacje/media/', so at
this point, your MEDIA_URL is wrong. MEDIA_URL needs to be 'http://
media.aplikacje/'
Or, you can change the server{} config for nginx to have the alias /
media
You shouldn't be running manage.py from within any other directory but the
top level project directory. That will screw up your PYTHON_PATH and
potentially cause conflicts.
Without seeing anything, if you go up a directory into just ~/webservices
and ran `python manage.py shell`, you should be
Looks like the server is having an issue. Connections on https are timing
out.
And upon looking at the last modified date on the wiki page for it... it
hasn't been updated in 3 years, so I'd safely say it no longer exists and
definitely wouldn't work with any modern version of Django.
--
You
You can't import a specific variable, you import the settings "package" and
access the variable from it:
from django.conf import settings
print settings.APP_NAME1
But as Calvin says, this should not change throughout the project. It's
essentially a constant.
--
You received this message becau
That is correct. The point of the separate subdomain is to help deployments
for the web. It's nicer and simpler sometimes to separate a domain or even
an entire server dedicated for media or S3.
On an intranet, you have a bit more flexibility. :)
--
You received this message because you are su
Try nginx and uWSGI instead of fcgi. http://projects.unbit.it/uwsgi/
--
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+
This is actually something new coming in Django 1.3, and by default is
requiring all AJAX request to define an X-CSRFToken header. Fortunately,
they've written about how to do it here and provided a jQuery
implementation: http://docs.djangoproject.com/en/dev/ref/contrib/csrf/#ajax
--
You recei
To get the token? It's stored in a cookie. You can read that in Javascript
with document.cookie, then parse the cookie string to retrieve the relevant
part.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to d
use django isn't
> serving the forms (which is when it usually sends the csrf cookie).
>
>
> On Mon, Mar 21, 2011 at 9:49 AM, Matt Robenolt
> wrote:
>> To get the token? It's stored in a cookie. You can read that in Javascript
>> with document.cookie, then par
Hmm, is Django and this static file on two separate servers? It's looking like
you might just want to do a @csrf_exempt.
On Mar 21, 2011, at 6:35 PM, Brian Craft wrote:
> No, it's not. It's a static file.
>
> On Mon, Mar 21, 2011 at 10:23 AM, Matt Robenolt
> wrote:
12 matches
Mail list logo
