New user/group options break everything

[philsturgeon]

This may well just be down to my environments, but since upgrading to 0.0.5 from 0.0.4 when the following lines were added, deploy and install have been utterly broken:

  :user    => node[:composer][:user],
  :group   => node[:composer][:group],

These were taking from apache www-data. I uninstalled apache (relying on that module sucks, and I don't use apache) but those users are the same for nginx, so that should not be an issue.

Since deleting those two lines, everything works fine. I presume its because www-data are not allowed to create temporary files outside of the web root. It would be nice if recursive ownership was applied to these files after deploy/install/update, but running the commands as anything other than root for me has just been a nightmare.

[geoffreytran]

That is most likely the case. By default it would take the user/group of the chef run, which caused permission issues, so I defaulted it to the apache module user/group.

In your case, I believe the best solution would be to override the node attributes in a role/environment. I'm open to any other suggestions.

[geoffreytran]

Looking at the logs, user/group options have been there since the cookbook was created. Could it be another issue with permissions?

[philsturgeon]

They definitely haven't http://d.pr/i/rn4V

I was coming from 0.0.2 to 0.0.5, not from 0.0.4, my bad.

Phil Sturgeon

On Tuesday, July 23, 2013 at 1:28 PM, Geoffrey Tran wrote:

Looking at the logs, user/group options have been there since the cookbook was created. Could it be another issue with permissions?

—
Reply to this email directly or view it on GitHub (#4 (comment)).