search

ajcrowe / puppet-supervisord

Puppet Module to install and configure applications under supervisord
MIT License
37 stars 104 forks source link

Allow running of supervisord as a non-root user #85

Closed brutus333 closed 8 years ago

brutus333 commented 8 years ago

If running supervisord as another user, it should be possible to change the configuration and look at log files. I change the ownership for supervisor.d and log directory.

ajcrowe commented 8 years ago

I think the problem here is that this would give the runtime user access to change it's own configuration by default. Given the expectation is you'll use puppet to deploy your chosen configuration it would be better practice to not allow this user to change things.

Perhaps it simply needs some additional parameters for this use case.

I have noticed that the permissions on the log directory are incorrect and should be 0755 which might resolve your log viewing issue?

brutus333 commented 8 years ago

Hello! In this case, what is the meaning of $user class parameter? BTW, I tried to set a non-root user to run supervisord (using $user parameter) but it is seems that startup scripts were not designed to be safely called for non-root user - the status endpoint will not return success. So puppet is spawning an unlimited number of supervisord daemons...

brutus333 commented 8 years ago

I am going to close this since it is not relevant anymore