Hi, Instead of using the same cache directory for the app/console commands and for webserver generated content, can't we make the following separation
- app/console -> cache in: app/cache/console/ (maybe with /dev and / prod) - webserver -> cache as it is right now, app/cache/ ( /dev and / prod) The next problem would be that app/console cache:clear/warmup won't work. As a solution for this we could have, in Sf2 SE, something like app_dev.php that's named app_cache.php that's secured the same way and just doest what the app/console clear:cache/warmup does right now. If I'm not clear enough let me know, I might try and explain it better/ make a proof of concept PR. Regards. On Jun 17, 3:32 pm, Jeremiah Dodds <jeremiah.do...@gmail.com> wrote: > On Thu, Jun 16, 2011 at 3:16 PM, Thomas Lundquist < > > thoma...@redpill-linpro.com> wrote: > > > And I like the "./app console symfony:server" approach, there are more than > > enough daemons out there so that making our own is not needed. > > > On the other hand, you can bet that quite a few will end up running that > > one > > in production, as one user, with everything owned by that user. > > > Which is not really any good idea. > > True, on the other other hand, quite a few will end up running really bad > setups in production no matter what. With this particular one, a check could > be added so it wouldn't start in production. Of course people could just run > their app in dev mode. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
