On 12/5/05, Rich <[EMAIL PROTECTED]> wrote: > i guess the real questions become: when using an egg on the production > server, where does the prod.cfg need to be placed and how can one issue > the tg-admin sql create command? I was trying to stay away from the > tarball and svn. I come from a java background and was hoping eggs > would be as painless or easier than .war files are in tomcat.
If you're running a standalone CherryPy/TurboGears server, eggs are plenty easy. If you're deploying behind Apache/lighthttpd, there's a bit more going on. (It's not unusual to deploy Tomcat behind Apache as well, though, so more setup is often needed there...) Basically, prod.cfg can go wherever you want your config file to be. When you deploy as an egg, your project's start script should wind up in whatever --script-dir you have on that system. You can run that start script and provide the path to the config on the command line. tg-admin sql create needs a bit more smarts about working on a production machine. When you run tg-admin sql create from within a project, TurboGears can figure out exactly what it is you're trying to do. From my read of the code, you *should* be able to do this: tg-admin sql -c /path/to/your/config create --egg YourProjectName however, I think it will complain about not being able to find the .egg-info directory, even though you're specifying an egg on the command line. That needs to be fixed. http://trac.turbogears.org/turbogears/ticket/180 If you have sqlobject-admin handy, you can run sqlobject-admin create, providing the dburi and the egg on the command line there. Kevin -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
