On 05 Dec 2005 09:35:35 -0200, Jorge Godoy <[EMAIL PROTECTED]> wrote: > > Swaroop C H <[EMAIL PROTECTED]> writes: > > > I guess I'm more comfortable with tarballs too, but that's mainly because I > > haven't used eggs before. Kevin, are eggs the recommended way of > > distributing _production_ TG code? If so, how would you make configuration > > changes and make sure they don't get overwritten when you upgrade an egg > > .... > > % unzip -t Controles_STCP-1.0-py2.4.egg | grep cfg > % > > There's no configuration file inside the egg, so you have to copy it by hand. > Take a look at http://trac.turbogears.org/turbogears/wiki/DeployWithAnEgg
Jorge is right here. That's the point of the config file: it sits outside of your code so that you can conveniently change the values there at the deployment site without worrying about code upgrades and the like. Anything that should move around with the app likely belongs in your Python, and anything that should be changed at deploy time belongs in the config. As far actual code copying mechanism: tarball, svn and eggs should all work fine. It's completely your preference. Kevin
