On Mon, Mar 24, 2008 at 2:16 AM, Wichert Akkerman <[EMAIL PROTECTED]> wrote: > I get the imporession that you are talking about migration types of > usage here. That is a very different problem than initial application > setup and is indeed best served differently, most likely in a way that > is much closer tied to the specific application. > > Initial setup is simple and predictable in most cases: create a > database, create some tables, load some initial data, maybe create a > file and directory or two. websetup/paster setup-app seems to be a good > standard way to do that.
The one thing setup-app is good for is building a standard environment for a publicly-distributed egg. But if you're building an app and deploying it on a server, or updating a server, there are alternative strategies that may be equally valid if not more so. > Perhaps it can be extended with a flag to make it refuse to run if it > has been run before, which will prevent people from accidentily zapping > existing data. At minimum setup-app needs command-line arguments, and I expect they'll be added in the next month or two. As for not running again, setup-app can do that itself by aborting if the database or directory it's creating exists or is not empty. You can also have it check an environment variable, although that's not very elegant for "clobber/don't clobber". The docs also need to be beefed up, but there's a major initiative on that ramping up now. -- 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 -~----------~----~----~----~------~----~------~--~---
