> OK.. so this assumes that you've run your app with the flag off at > least once (to get agavi to compile the config caches), and then turn > the flag off. Hmm.. It just seems kludgy to me. Now if we had a > phing task which would create the config caches (not even sure if > that's possible.. I haven't had my coffee yet), I would buy this in a > heartbeat. Whaddya think?
Hmmh. Well... we could actually do this, yeah, since all config files are defined in config_handlers.ini. So we would take this file, look if the configs are there, and compile everything after flushing the cache. This sounds good. We'll have to pay attention to module configs etc and maybe "*" wildcards, but it should be possible. Might look into that later... Proposal: I back this DONT_COMPILE_TEH_CONFIGS_YOU_RETARD flag out, and we add such a functionality together with the phing task in 0.11. I could also imagine this: with AG_DEBUG set to off, config checks aren't performed, nothing is compiled etc, and you'd have to call the task manually. I think this is even better, isn't it? In production environments, configs change almost never, so it would be fine to do it this way. - David _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
