Ian Wilson schrieb: > Thanks I think I am finally getting it now. So for my installation > the prod.cfg should go here: > /usr/lib/python2.4/site-packages/projectname-1.0-py2.4.egg/
I'm afraid not. > I think that is why this has the note: "needs work, how to configure" > http://docs.turbogears.org/1.0/DeployWithAnEgg > because the prod.cfg file is mentioned as required but it never tells > you really where to put it. Because you can put it wherever you like, it just has to be either in the directory "from where you start* start-project.py (i.e the current directory), or you have to specify its location on the command line for start-project.py. The current directory of the start-project.py script is *not* the the egg-directory nor the directory, where the start-project.py script is installed (usually /usr/bin or /usr/local/bin), but the directory from where you call it. But you're right in that egg deployment currently does not address this problem, and that's why you have to copy the config file by hand. You could put a default configuration file in the egg (by including it somewhere below your project package directory) and then locate it in your start script with the pkg_resource module, but I haven't seen a ready-made recipe for that yet. HTH, Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
