Matt Palmer wrote: >>>> Considering that various other parts of Rails recommend 0666 perms on >>> log >>>> files, I'd say it was definitely deliberate. Ill-advised, definitely, >>> but deliberate. >>> Hmm, but why would rails ever recommend something that is ill-advised? :-D >> My guess would be to support FCGI processes that are running the same use as >> Apache which would usually be a different user and group from the user >> uploading and deploying the application files. > > Solved on all my servers with: > > chgrp -R www-data log tmp > chmod -R g+w log tmp > > - Matt
Actually, after digging into this a bit more, it's not really Rails' fault. The rails command does create a production.log, but most people don't actually check that in to their repository or deploy it. Rather, the Ruby Logger class creates the file on the fly when the app is started. This is creating the file as 0666. I would still like to figure out some way to configure Logger to do 0660 rather than have to rely on chmod-ing after the fact. But, that's clearly something I should take up with the Ruby folks. thanks for you answers... Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
