On Sat, Sep 8, 2012 at 9:49 AM, Reginald Choudari
wrote:
> Django doesn't serve files itself; it leaves that job to whichever Web
> server you choose.
> We recommend using a separate Web server -- i.e., one that's not also
> running Django -- for serving media. Here are some good choices:
some ti
If you are using only Apache with mod_wsgi, you will also need to set up
Aliases for your media directories (like css, images, or user-uploaded
files). This is because mod_wsgi doesn't serve static files, it is only
used to generate the dynamic pages of your site. It's perfectly possible to
use
Hi,
The apache or whatever the webserver you choose, should only serving static
files, not .py files .
the / request to your webserver will be redirect to django process, whether
it is uwsgi, or wsgi , or whatever service you choose to deploy.
Django runs as application server actually.
user --
Hello,
I've just started working on deploying a Django hosted website on my VPS.
Last night I finished configuring mod_wsgi with apache2.2 and had got the
'It works!' page running from my Django project. I read here (
https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/modwsgi/) the
fol
4 matches
Mail list logo
