On Mon, Jan 10, 2011 at 8:23 PM, Todd Wilson <[email protected]> wrote: > Thanks again. For these student accounts, performance is not critical, > but uniformity is. However, if a student creates a project that > outlasts a particular semester, or for some reason needs extra > performance, I wouldn't mind moving it to a different place and serving > it more efficiently.
I would look at using Puppet (or another programatic solution) to provision the WSGI configuration components. You could require that students request the WSGI service before using it, and then if they request it, deploy the necessary files and refresh httpd. Most of the stuff that needs to be deployed per user instance should be pretty self contained, and having a script or configuration management system provision that stuff will ensure that things are done uniformly. Puppet can be used to manage an entire system, but you can also use a very scaled back configuration to manage just httpd, or even just the mod_wsgi files that each user requires. -- 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.
