I'll take a look and see if I can put together anything generic enough to be
useful. I'd hope that generally, CLI scripts would use models rather than
calling anything in the controller, and generally, the ACL stuff would all
be in the controller. But that's just the way I do it, I guess having
The issue I have had in the past is when a CLI is trying to leverage an admin
module that uses the standard Auth / ACL logic. It expects a login process
to populate some username and password information that get passed to the
Auth code.
It would be nice to see the "best practice" for having an
OK, I can certainly look at that.
Generally, you'd set the file permissions on the script so it can only be
run by the specified user(s) - so, for instance:
shell# chown admin_user:admin_group myScript.php
shell# chmod 744 myScript.php
shell # ls -al
-rwxr--r-- 1 admin_user admin_group 3212 Apr
should optionally require admin credentials passed as arguments or should
confirm CLI is being run by particular system users (e.g. root).
lightflowmark wrote:
>
> I'm actually working on a proposal to do exactly this at the moment.
>
> What features would people like to see on this?
>
> Curr
Hello,
>
> I'm actually working on a proposal to do exactly this at the moment.
>
> What features would people like to see on this?
>
> Currently, the proposed Zend_Schedule component will:
> 1) be run via CLI scripts from the cron
>
> 2) uses Zend_Application to load the bootstrap of an exist
I'm actually working on a proposal to do exactly this at the moment.
What features would people like to see on this?
Currently, the proposed Zend_Schedule component will:
1) be run via CLI scripts from the cron
2)uses Zend_Application to load the bootstrap of an existing application
to loa
