Create a 'pulp' user for Pulp3 in the development environment
In Pulp2 /var/lib/pulp was owned by the apache user. For Pulp3 we do not want to be limited to apache as the server thus having an 'apache' user own the directory and our processes makes little sense.
Note: This ticket is for the developer environment only. Changes to a production Pulp environment are being tracked in part as issue #2840.
Our Pulp devel environment should create a
pulp user to own /var/lib/pulp and the running celery processes.
vagrant ssh should switch to using the 'pulp' user automatically by configuring the Vagrantfile with
#4 Updated by mhrivnak over 3 years ago
Is this scoped only to the development environment? The solution reads that way, but the title and problem does not.
Maybe that's just because we can't do anything else right now. What actions do we need to take for this to apply also to production deployment? Maybe all we can do at this point is create one or more tasks to do this when we get around to RPM packaging, add documentation, etc?
#5 Updated by bmbouter over 3 years ago
We should also have the supplied apache config file run any WSGI processes as the pulp user.
This ticket is for making improvements to the dev environment which probably won't get Apache any time soon. We need to have the WSGI processes run as the Pulp user configured as part of the production Ansible work which can be done right after #2840 and when the configs are available.
Please register to edit this issue