On Jan 31, 2007, at 7:23 PM, Chris Shenton wrote:
> > My application has two parts, a webapp, and a bunch of commandline > programs that do a bunch of analysis; they both talk to the same > SQLAlchemy-fronted DB, and both reference files from each other. > The commandline tools all live under .../lib/* so they could be made > part of the egg. > > I've built and deployed an egg before and served it up with Apache and > mod_python, but -- since this is new to me -- I don't know how I would > do this and accommodate all the commandline tools that I'll need to > run from cron and elsewhere? > > Sorry if this is obvious, but it's just not clear to me. I don't > really understand eggs that well yet. > Your project's setup.py can call the setup function with a 'scripts' argument. These scripts will be installed the the PREFIX/bin/ directory. scripts is a standard distutils argument. Egg installs will do some special tinkering with scripts, basically just so it gets the correct .egg dependencies, but otherwise it works the same as when installed without using setuptools/eggs. There's plenty of examples of this out there, PasteScript comes to mind (it installs a 'paster' script). -- Philip Jenvey --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
