On Fri, Feb 22, 2008 at 11:06 AM, Brian Granger <[EMAIL PROTECTED]> wrote: > We have two pylons apps that we want to combine using a composite > app. One of our pylons apps has a database that needs to be setup > using the standard 'paster setup-app' command.
I have doubts about whether setup-app is really worthwhile. An alternative is to make a scripts/ package in your application and run them with "python -m". Or you can get fancy and set up entry points to make them normal executables. The problem with setup-app is it can only do one thing, and that thing may be wrong when copying an existing deployment or updating it. For instance, you may have to create the database tables, or reset the data to an initial state, or add a column or modify its type without disturbing existing data. Or you may have to reinitialize some tables but not others, or set up some data files, etc. if setup-app took arguments it could handle all these cases, but it doesn't. In any case, I'm leery of running a setup-app that may stomp over stuff I forgot it did, so I'd rather run several individual scripts that each do one thing, and can take arguments. For instance, you may want to pass a different database URI on the command line than you'd normally use, to get extra admin privileges without putting the password in a config file. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
