Erik Allik wrote:
> I don't think virtualenv will help you set up your project running
> with Apache. But it's a good practice nevertheless.
Yes virtualenv can be used to get it to work. The problem is that one
can't explain the way it would be used without the OP posting how the
hosting service has mod_python configured to allow him to run a Python
web application in the first place.
FWIW, any hosting service that offers shared hosting for different
users under the same Apache instance probably doesn't know what they
are doing and you'd probably want to avoid them. This is the case as
mod_python isn't safe to use for shared hosting for unrelated users
who you can't trust as neither running code nor writable areas of
filesystem are isolated from each other. Do you really want to trust
your application to a web hosting service that either doesn't realise
this or doesn't care enough to setup their systems so your application
is properly protected.
Graham
> If your hosting provider supports custom FastCGI handlers/processes,
> you could look into setting up Django with FastCGI. It's quite easy.
> Also if you don't have a way to set up FastCGI (or mod_wsgi or
> mod_python but I doubt your hosting provider lets you do that if
> they're not a Python hosting provider) but your hosting has a cgi-bin
> directory, you can use that to get up and running. It uses plain CGI
> which would be slow if your whole Django project code was to be loaded
> on each request, but there's a nifty little tool called cgi-fcgi which
> routes CGI requests so a persistent FastCGI process which it can spawn
> itself as needed. Just as with "true" FastCGI, this will enable you to
> set up a completely customized environment for your project.
>
> If you have SSH access to the hosting machine which you hopefully do,
> you should be able to compile anything you might need for the
> environment such as database drivers or PIL and any other extensions
> that require compilation.
>
> Regards,
> Erik Allik
>
> On 26.09.2008, at 1:39, Graham Dumpleton wrote:
>
> >
> > On Sep 26, 8:26 am, "Xian Chen" <[EMAIL PROTECTED]> wrote:
> >> Hi,
> >>
> >> I want to run my Django app on a shared web server.
> >>
> >> As so many people share this server, I install python and
> >> Django(1.0) under
> >> my home directory.
> >>
> >> How can I configure the Apache with mod_python to make the django
> >> under my
> >> directory running?
> >>
> >> The server administrator refused to install Django in the /usr/bin
> >> directory
> >
> > With mod_python you cannot make it use a different Python installation
> > than the one it was compiled with. The best you can manage is to use
> > virtualenv to build a Python virtual environment in your home
> > directory where you install all the Python modules/packages you want
> > and then refer to that.
> >
> > http://pypi.python.org/pypi/virtualenv
> >
> > Only problem I see is that documentation for virtualenv seems to have
> > changed lately and no longer mentions the easy approach for using it
> > with mod_python. It has some new mechanism mentioned which I can't see
> > at the moment how it works.
> >
> > Graham
> > >
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
