I never used the option, so I'm not sure what it does exactly, but app.config has a "cache_warmer" option (can be, "true", "full" and "false), which defaults to the opposite of kernel.debug (so "false" for debug kernels). I believe router and templating sections also have cache_warmer sub-options, but those are just booleans (true/false). Might be worth a shot to play around with that and see if it helps.
On Mon, Feb 7, 2011 at 5:02 AM, Ruudk <[email protected]> wrote: > I think I missed something about the new cache warming functionality. > Everytime I add a new templates I have to run "console cache:warmup" to get > them working. > > Is there a way to automate this in a dev environment? > > -- > 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 [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 > -- jeremy mikola -- 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 [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
