Setting up Django on GoDaddy Deluxe Shared Hosting

Has anyone had success in setting up Django on GoDaddy's
Deluxe shared
hosting plan?  It supports Python CGI, but has no shell
access. I read
a previous post from October 2006, where I read of another
user who
did the same things I did (guided by the django
documentation for
shared hosts), but now I'm stuck. I'm hoping someone has
managed more
success than this since October 2006.

I created a "myaite.fcgi" script, but I was
confused by some of the
items.  For example, adding the custom Python path with
"sys.path.insert(0,"/home/user/python")"
- what is that?  If python is
already installed at "/usr/bin/python", what would
this do?

And I don't even know if fastcgi is accessible for python. 
I come
from a .Net/Java background and everything apache- and
cgi-based is
quite foreign to me.

And I know I could switch to a different host, but I already
have
several other domains hosted at godaddy and would prefer not
to have
to change hosts to use Django.

Thanks for any direction you guys can offer (even if it's to
tell me
it's not possible).

Donald H.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

> Has anyone had success in setting up Django on
GoDaddy's Deluxe shared
> hosting plan?  It supports Python CGI, but has no shell
access. 

CGI != FastCGI != WSGI

If all they offer is CGI, the general consensus is that you
ought
look elsewhere as (1) it's not supported in Django and (2)
if it
was supported in Django, performance would be abysmal in an
off-the-charts sort of way.  A new python process is started
for
each request, all the code is hauled into memory for one
request,
and then disposed of.  Not bad for small sites with
low-volume
traffic.  But it easily gets swamped.  A  better alternative
is
to have the python interpreter stick around with your code
in
memory once and then pass requests to the existing code. 
Enter
FastCGI, WSGI and mod_python to solve this problem, each in
its
own way.

Python does do CGI, FastCGI and WSGI as well as the obvious
mod_python. 

Django/Python does FastCGI and WSGI as well as mod_python.

> And I don't even know if fastcgi is accessible for
python.  I come
> from a .Net/Java background and everything apache- and
cgi-based is
> quite foreign to me.

Hopefully the above description helps clarify the
"fastcgi !=
cgi" confusion here.


I don't know what GoDaddy offers in the package you are
using.
If it's CGI, your outta luck.  However, if they do offer
FastCGI
or WSGI, you're in luck (nothing you mentioned sounded like
they
offered mod_python).

-tim



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Thanks for the quick and thorough response, Tim!

I'll find out if the FastCGI they advertise as being
available for
Ruby on Rails could also be made accessible to Python by
following the
Shared Hosting instructions at the bottom of 
http://www.djangoproject.com/documentation/fastcgi/.





On Dec 28, 4:35 pm, Tim Chase <django.us...tim.thechases.com> wrote:
> > Has anyone had success in setting up Django on
GoDaddy's Deluxe shared
> > hosting plan?  It supports Python CGI, but has no
shell access.
>
> CGI != FastCGI != WSGI
>
> If all they offer is CGI, the general consensus is that
you ought
> look elsewhere as (1) it's not supported in Django and
(2) if it
> was supported in Django, performance would be abysmal
in an
> off-the-charts sort of way.  A new python process is
started for
> each request, all the code is hauled into memory for
one request,
> and then disposed of.  Not bad for small sites with
low-volume
> traffic.  But it easily gets swamped.  A  better
alternative is
> to have the python interpreter stick around with your
code in
> memory once and then pass requests to the existing
code.  Enter
> FastCGI, WSGI and mod_python to solve this problem,
each in its
> own way.
>
> Python does do CGI, FastCGI and WSGI as well as the
obvious
> mod_python. 
>
> Django/Python does FastCGI and WSGI as well as
mod_python.
>
> > And I don't even know if fastcgi is accessible for
python.  I come
> > from a .Net/Java background and everything apache-
and cgi-based is
> > quite foreign to me.
>
> Hopefully the above description helps clarify the
"fastcgi !=
> cgi" confusion here.
>
> I don't know what GoDaddy offers in the package you are
using.
> If it's CGI, your outta luck.  However, if they do
offer FastCGI
> or WSGI, you're in luck (nothing you mentioned sounded
like they
> offered mod_python).
>
> -tim
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Here's what I asked GoDaddy Support:

"Is FastCGI accessible from python scripts if I add my
own handler? I
ask
this in specific relation to setting up Django. Is this
known not to
work?"


Here's their response:

"FastCGI is accessible from Python scripts for our
Linux hosting
accounts. We do not allow, however, the addition of a custom
FastCGI
handler in our shared hosting accounts."


Does this mean I am definitively out of luck?


Thanks again for your help.



On Dec 28, 6:17 pm, Donald H <donald.hug...gmail.com> wrote:
> Thanks for the quick and thorough response, Tim!
>
> I'll find out if the FastCGI they advertise as being
available for
> Ruby on Rails could also be made accessible to Python
by following the
> Shared Hosting instructions at the bottom of
http://www.djangoproject.com/documentation/fastcgi/.
>
> On Dec 28, 4:35 pm, Tim Chase <django.us...tim.thechases.com> wrote:
>
> > > Has anyone had success in setting up Django
on GoDaddy's Deluxe shared
> > > hosting plan?  It supports Python CGI, but
has no shell access.
>
> > CGI != FastCGI != WSGI
>
> > If all they offer is CGI, the general consensus is
that you ought
> > look elsewhere as (1) it's not supported in Django
and (2) if it
> > was supported in Django, performance would be
abysmal in an
> > off-the-charts sort of way.  A new python process
is started for
> > each request, all the code is hauled into memory
for one request,
> > and then disposed of.  Not bad for small sites
with low-volume
> > traffic.  But it easily gets swamped.  A  better
alternative is
> > to have the python interpreter stick around with
your code in
> > memory once and then pass requests to the existing
code.  Enter
> > FastCGI, WSGI and mod_python to solve this
problem, each in its
> > own way.
>
> > Python does do CGI, FastCGI and WSGI as well as
the obvious
> > mod_python. 
>
> > Django/Python does FastCGI and WSGI as well as
mod_python.
>
> > > And I don't even know if fastcgi is
accessible for python.  I come
> > > from a .Net/Java background and everything
apache- and cgi-based is
> > > quite foreign to me.
>
> > Hopefully the above description helps clarify the
"fastcgi !=
> > cgi" confusion here.
>
> > I don't know what GoDaddy offers in the package
you are using.
> > If it's CGI, your outta luck.  However, if they do
offer FastCGI
> > or WSGI, you're in luck (nothing you mentioned
sounded like they
> > offered mod_python).
>
> > -tim
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---