Generally if doing this each application would be done in a chroot of its own for best isolation, at which point virtualenv's are possibly redundant as the user can have access to the chroot itself and so just install stuff within system wide Python of the chroot. You can still you virtual environments if don't want to do that.
Exactly what you do really depends on what you are trying to achieve and you haven't explained that, only explaining the solution you want but not the goal. Graham On 27 June 2011 16:02, avetis.kazarian <[email protected]> wrote: > Then I guess if I use it with a virtualenv I should be able to jail > each project easily? > > On Jun 27, 2:10 am, Graham Dumpleton <[email protected]> > wrote: >> Python itself has no ability to constrain access to a specific part of >> the file system. Any sort of restricted environment within the context >> of a Python process is basically impossible and circumventable. You >> thus have to rely on using operating system mechanisms for setting up >> chroot jails. The daemon mode of mod_wsgi has an ability to have the >> daemon process run in a proper chroot jail if that is of interest. >> >> Graham >> >> On 27 June 2011 03:34, avetis.kazarian <[email protected]> wrote: >> >> >> >> >> >> >> >> > Well, actually I don't think that WSGIScriptAlias does anything like >> > open_basedir. >> >> > The idea behind open_basedir is the jail all script within a set of >> > paths. >> >> > For instance, if you have put in your configuration file open_basedir=/ >> > my/path/:/my/other/path or the equivalent version as apache vhost >> > directive in your vhost file, any call to functions which handles >> > files and which would try to access to files outside these paths would >> > end with an error. >> >> > It's an easy and very simple way to jail your projects. >> >> > I'm pretty sure there is a way to jail a Python project as it is with >> > a PHP one. >> >> > But as I'm a rookie with Python, it's still PIA to make it run as I >> > would with PHP. >> >> > On Jun 26, 4:57 pm, wongobongo <[email protected]> wrote: >> >> Have you seen WSGIScriptAlias? >> >> >>http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIScr... >> >> >> On Jun 26, 5:01 am, "avetis.kazarian" <[email protected]> wrote: >> >> >> > Hi, >> >> >> > I'm looking for an equivalent of the PHP's open_basedir >> >> > —http://en.php.net/manual/en/ini.core.php#ini.open-basedir—but for >> >> > WSGI. >> >> >> > Is there anything like that? >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "modwsgi" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group >> > athttp://groups.google.com/group/modwsgi?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
