Received: by 10.52.91.17 with SMTP id ca17mr24211252vdb.1.1330490584328;
        Tue, 28 Feb 2012 20:43:04 -0800 (PST)
X-BeenThere: django-users@googlegroups.com
Received: by 10.52.65.194 with SMTP id z2ls6697405vds.5.gmail; Tue, 28 Feb
 2012 20:42:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.70.242 with SMTP id p18mr2679773vdu.18.1330490547322; Tue,
 28 Feb 2012 20:42:27 -0800 (PST)
Authentication-Results: ls.google.com; spf=pass (google.com: domain of
 ays...@gmail.com designates internal as permitted sender)
 smtp.mail=ays...@gmail.com; dkim=pass
 header...@gmail.com
Received: by y10g2000vbn.googlegroups.com with HTTP; Tue, 28 Feb 2012 20:42:27
 -0800 (PST)
Date: Tue, 28 Feb 2012 20:42:27 -0800 (PST)
In-Reply-To: <CAFkDaoRBjmvZfxa2M3ZM75zfh54WJokg8=E-aVOXxyvszSYXmg@mail.gmail.com>
References: <1d18e3a3-8a2d-4513-86fe-ee416e60e8b6@j5g2000yqm.googlegroups.com>
 <1106732.2657.1330357153222.JavaMail.geo-discussion-forums@ynjc20>
 <6e5e0d9e-b510-45ca-bf86-c4af550a186b@gr6g2000vbb.googlegroups.com>
 <CAFkDaoSLBTojpnWi1H5gcG3nd65C=Y3yvibysVmo=kfGLdLM4w@mail.gmail.com>
 <55759ad7-a057-4ba0-abb9-a6037e7f2c7a@s13g2000yqe.googlegroups.com> <CAFkDaoRBjmvZfxa2M3ZM75zfh54WJokg8=E-aVOXxyvszSYXmg@mail.gmail.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.0) AppleWebKit/535.11 (KHTML, like
 Gecko) Chrome/17.0.963.56 Safari/535.11,gzip(gfe)
Message-ID: <deeacd02-bde9-4a48-a195-a9dc2ac70e6c@y10g2000vbn.googlegroups.com>
Subject: Re: Going crazy with WSGI
From: atlastorm <ays...@gmail.com>
To: Django users <django-users@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks a lot, Javier. Things are a lot clearer now. Appreciate it.

On Feb 28, 7:46=A0pm, Javier Guerra Giraldez <jav...@guerrag.com> wrote:
> On Tue, Feb 28, 2012 at 5:58 AM, atlastorm <ays...@gmail.com> wrote:
> > Right now I'm practicing Django by running the Django server
> > (manage.py runserver) and everything works. Apache also runs but I
> > have no clue what its doing.
>
> nothing.
>
> the Django development server (the one that runs with the runserver
> command) is an intentionally-limited web server. =A0you don't need
> Apache for development. =A0but this server will absolutely not be
> appropriate for real world serving, no matter how light the load.
>
> > If I close the Django server, how do I
> > run my application? If I save a django.wsgifile in mysite/apache/
> > django.wsgiwill things happen automatically?
>
> you need the mod_wsgi docs for that. =A0the Django page about deployment
> in mod_wsgi should be enough to get you running in the simplest case.
>
> > When I practiced CGI with python, I had to import the cgi module and
> > use that to get the inputs from an html form. Do I have to do
> > something similar with Django?
>
> no. =A0Django manages everything betweenWSGIand your apps. =A0you
> shouldn't need any extra Python code besides what you run under the
> development server. =A0 in fact, the development server usesWSGItoo,
> so if your code already runs there, it should also run on
> Apache/mod_wsgi once you get that configured.
>
> --