I remember that conversation. I see a lot in there about umask, changing users, etc - nobody really seemed to have an easy solution (so I wanted to ask again). We have a pretty GUI configuration setup in the standard distribution, but I need to create a new unix group or change umask to clear my cache?
Thanks! Ryan Weaver US Office Head & Trainer - KnpLabs - Nashville, TN http://www.knplabs.com <http://www.knplabs.com/en> http://www.thatsquality.com Twitter: @weaverryan On Wed, Apr 13, 2011 at 4:45 PM, Johannes Schmitt <[email protected]>wrote: > see > http://groups.google.com/group/symfony-devs/browse_thread/thread/b1f2f5d3b684ca25/e0b649d3379da4f9?lnk=gst&q=cache+permissions > > On Wed, Apr 13, 2011 at 11:37 PM, ryan weaver <[email protected]>wrote: > >> Hey folks! >> >> I'd like to hear what the "proper" workflow is for clearing the cache and >> making sure the permissions work for both the CLI and the web server. Maybe >> I'm just missing an obvious step - either way we can doc it so nobody gets >> confused. >> >> Basically, the cache needs to be writable by the web server as well as >> your CLI user. In my setup - which I think is typical - my webserver and cmd >> line user are not the same. Here are the problems I'm seeing: >> >> * Clearing the cache requires root, as cache files have been created by >> the web server, they're not writable by my CLI user. So, the clear cache >> task fails (in a very ugly way) when run as my normal user >> >> * After a root cache clear, I have to chmod (or chown) the cache dirs so >> that the webserver can write to the cache >> >> So, it's a little awkward. What *should* the workflow be. Making my >> webserver and cmd line user the same is not an option - I'm looking for the >> workflow that works out-of-the box for your average user. >> >> Thanks! >> >> Ryan Weaver >> US Office Head & Trainer - KnpLabs - Nashville, TN >> http://www.knplabs.com <http://www.knplabs.com/en> >> http://www.thatsquality.com >> Twitter: @weaverryan >> >> -- >> 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 >> > > -- > 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 > -- 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
