On Mar 25, 5:11 pm, Graham Dumpleton <graham.dumple...@gmail.com>
wrote:
> 2009/3/26 Duncan <caphec...@gmail.com>:
> > On Mar 24, 7:28 pm, Graham Dumpleton <graham.dumple...@gmail.com>
> > wrote:
> >> 2009/3/25 Duncan <caphec...@gmail.com>:
>
> >> > Are there any issues that I might run into with 300+ virtual hosts,
>
> >> Are you currently using mod_python with 300+ virtual hosts with a
> >> Python web application hosted in each site?
>
> >> > or
> >> > anything I might need to be aware of beyond what's in the mod_userdir
> >> > thread I linked?
>
> >> There have been various other discussions which may be relevant and a
> >> better source of information. Depends a bit on what some of the goals
> >> are.
>
> > I'll trawl the group again to make sure I didn't miss anything.
>
> >> > It looks like this will be a good solution for my users and I just
> >> > want to make sure the transition is as smooth as possible.
>
> >> A few questions.
>
> >> How much memory are the Python applications running under each virtual
> >> host likely to take? This will be a factor if there are 300 of them.
>
> >> Are those applications likely to be used constantly and thus always
> >> need to be resident, or are they likely to be infrequently used and
> >> thus don't strictly need to always be running? This plays into the
> >> memory question as far as solutions to trying to reduce memory usage.
>
> >> Do the applications running under each virtual host need to run with
> >> the permissions of a specific user who is the owner of that account?
>
> >> Answer that to clarify things and will see if can find better past
> >> threads where this has been discussed.
>
> > Graham,
>
> > Sorry for not including much data when I first posted; I wasn't sure
> > what was relevant. We provide shared hosting, so our users work with
> > the applications that meet their needs, be they PHP, Rails, or Python.
> > This is not a homogenous environment, so even with mod_wsgi we
> > wouldn't have every user running the same applications. If it's
> > relevant, we're also looking at adding support for frameworks like
> > Django, pylons, and turbogears.
>
> > I think at the moment no more than fifty of our sites are using Python
> > apps; we have Trac installs, fckeditor, bblog, firestats, bugzilla,
> > and some applications developed by users. Applications should run with
> > the permissions of the account they're run under; we use suexec for
> > PHP applications already. RAM usage is not a primary concern at this
> > time, since we're not primarily a Python host.
>
> Okay, one more question. Is whether they want to use Python as web
> application language something they have to opt in for in some way, or
> is that decision purely up to them and they would start using Python
> without you even knowing?
It's purely up to them; the only time we'd hear about what language
they're using is if there's a security issue or they ask for
assistance installing the software.
Duncan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to modwsgi@googlegroups.com
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en
-~----------~----~----~----~------~----~------~--~---
