> Since lots of stuff gets modified and added, as part of the > application execution, I think it is best to have the application > installed in the home of the web-server user, not as root. This allows > to set user quotas, prevent /usr/lib/python2.4/site-packages/ from > filling up with junk and, I think, is less likely to lead to security > issues. > > Does this make sense?
Yes! Personally I don't install my web application packages to a system location either. For deployment I generally create a dedicated user, and run everything out of a directory under that users $HOME. This also makes it easier to have multiple versions of the application running in parallel (production and qa instances say). > When a web application generates lots of extra stuff that gets stored > for a while (e.g., temporal files with results ---ours are a bunch of > bioinformatics applications: http://asterias.info), what is the most > appropriate place to install the egg? I should mention, if you are making a pylons application to integrate a bunch of different bioinformatic tools, you might want to check out our 'galaxy' project (http://g2.bx.psu.edu) which just happens to be... a python/wsgi project for integrating a bunch of bioinformatics tools (the framework predates pylons, but is paste based and is evolving toward being almost exactly like pylons). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
