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.
We use SVN-based deployment. The obvious advantage is that switching between revisions is cheaper - in the best case, you just transfer a diff over the wire.
I wouldn't say though that with todays bandwidths this is much of an issue, egg-deployment is just fine.
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?
That should work out of the box. Eggs are unzipped, and toscawidgets + TG are set up to serve their contents.
However, if you fiddled with your setup.py & made the egg zip_safe, it won't be unzipped, and serving fails.
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?
No. And honestly - 3 files are "scattering"? I dimly remember a bazillion config-files in JBoss-land, *that* was scattering :)
Diez -- 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.
