yep, separate cache folders work. overhead shouldnt be an issue. thanks a lot!
cheers, john -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of David Zülke Sent: Sonntag, 8. Februar 2009 17:15 To: Agavi Users Mailing List Subject: Re: [Agavi-Users] Secure cronjob | Best practice No, that would work. You need, however, set that different dir in index.php/console.php before you call Agavi::bootstrap(). My guess would be that it works if you make the CLI call first, and then a call from the web, though that's not really a proper solution to the problem :) Am 08.02.2009 um 17:01 schrieb Veikko Mäkinen: > David Zülke wrote: >> Yes, that has to do with folder permissions. The web server process >> creates cache files with certain permissions, and also the folders >> inside (in your case, it's likely config/ inside cache/). Now the >> command line interface wants to create folders there, but can't. >> Can't >> say how to solve this off the top of my head, but it's doable... >> > > For a quick fix you can of course set the cache directory to something > different for console context. The overhead shouldn't be an issue if > you are running some occasional maintenance tasks or something. > > Or has this solution some downsides I'm not aware of? > > -veikko > > -- > Veikko Mäkinen > [email protected] > 044 5910 413 > http://blog.veikko.fi > > > _______________________________________________ > users mailing list > [email protected] > http://lists.agavi.org/mailman/listinfo/users > _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
