I'm new to TurboGears and Python in general, so bare with me:-) I have been enjoying TurboGears 2.1 for a few weeks now, after giving it a chance over the various JVM frameworks I'm familiar with. So far, I like it.
Now comes the time when I want to deploy the app with mod_wsgi and am having troubles understanding a few details. One of my issues is that I think I want to deploy as an egg vs. source, unless someone can convince me otherwise, I think the egg package is rather close to what java's jar provides and is super convenient. I created two virtual envs, BASELINE and myapp, as in the docs and installed TG and myapp into the myapp virutal env. That works. Now, I have a production.ini file at the root of myapp and have properly configured mod_wsgi. So what's my issue you may ask? Well, first, my static files are packaged in the egg file and I don't want to (at least at this point) serve them directly from apache. Is there a way to serve these statics from an egg? Second, I don't like having all these files scattered all over the place, place production.ini here, place wsgi script here, etc... Is there a way to just deploy an egg and configure mod_wsgi to find everything it needs there? Sorry, the docs seem a bit scattered to me when it comes to a coherent deployment strategy, though it might just be my lack of understanding. Any help through a reply and/or pointing me towards some instructions would be much appreciated. --Ilya -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
