On 4/6/07, David Geller <[EMAIL PROTECTED]> wrote:
> I would submit that if there is not a better way of doing this, there
> *should* be.
>
> Most applications have several pieces - *one* (or several) of them are
> contained in the web part, which is the part pylons especially
> addresses. But then there could be bunches of different
> "maintenance"/"admin"/auxillary functions, many of which are
> command-line programs (or, even, desktop/gui programs), all using the
> same model and other application structures. Examples include database
> import/export, integrity checks, database alters, etc.
>
> I am sure it is not possible to create a "standard" which would satisfy
> every requirement in all conditions, but we might be able to come up
> with a scheme which is both simple and straightforward, and flexible at
> the same time.

That's what I and others have asked for repeatedly under the name
"admin scripts".  But there doesn't seem to be a compelling way.

1) Setuptools scripts: won't work if you don't install it as an egg.
Mixes scripts for one site with other bin scripts.

2) Paster commands: a bit of work to set up.  Not sure if you can make
paster commands private to one site.

3) bin directory in application: that's what I've done in my
non-Pylons sites but it's not egg-friendly.

There's also the config/model/globals headache: you have to do
everything "paster shell" does.

So far every time I've needed a Pylons admin script, I've found a way
to put the functionality into the application, but I know that won't
be true forever.

I'm not sure if it's Pylons' problem or Paste's problem.

-- 
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to