On 29 Mai, 20:44, Dustin Whittle <[EMAIL PROTECTED]> wrote: > Matthias, > > This is because there is no cli environment by default. Only prod, dev, and > test. The concept of a cli environment does work well with a *web* > framework.. I see the point for the command line and executing tasks, maybe > Fabien can clarify?
I have yet another theory: My project doesn't work well *without* cli/ cron/etc. ;-) Hm.. would at least be useful to be able to configure the default env of tasks as for me it doesn't make any sense to use test environment with cli stuff in production. regards Matthias > > On 5/27/08 6:43 AM, "Matthias N." <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > just would like to understand why the default environment of a task is > > "test"? > > Wouldn't it make more sense to make it "cli"? > > > Now I always need to provide a useless option to change this to "cli" > > - this seems to be odd. > > > regards, > > Matthias --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
