Hi, I would like to second that. Moreover, currently the log-rotate task disables the application and doesn't enable it again afterwards (btw, is this by design?).
One could argue that it's easy to directly remove the lock file, but I also don't see the need to clear cache when enabling the app again. When needed, I think it should be called explicitly. Cheers, Paulo M Alexey Kupershtokh wrote: > Hi all. > > IMHO the project:enable task shouldn't execute cache:clear. > > My rationale is that I currently have no way to precache something > useful before returning my project back to the enabled state. It's usual > practice for highload projects. Otherwise running such project with > empty cache can lead to the case when every of concurrent requests will > try to compile configs, etc... So the project will experience much > higher load during the first seconds. > > Currently I trend to write my own task for enabling project. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
