Issue #3050
closed
get rid of "apache" user in dev environment
Status:
CLOSED - CURRENTRELEASE
i thought we on purpose wanted to get rid of apache user to give the possibility to use nginx for example as well.
@ipanova, so do you think we ought to change the dev environment to "pulp" user also?
yes, that's my understanding
- Tags Dev Environment, Pulp 3 added
- Sprint/Milestone set to 45
- Triaged changed from No to Yes
- Status changed from NEW to ASSIGNED
- Assignee set to daviddavis
Currently in our dev environment, we have two users: vagrant and apache. We're running pulp (via runserver) as vagrant while apache owns the files and runs the processes pulp_workers, etc.
Two options I see:
1. We create a new pulp user in ansible and have it own the files, processes, etc
2. Replace BOTH the vagrant and apache users with a pulp user
I have option 1 working now. It's a rather minimal change. Option 2 is a radical change and I'm not 100% sure it might work.
Thoughts?
Discussed with bmbouter, @dkliban, and @asmacdo in person and am going to try option 2.
- Related to Task #3065: Replace the vagrant user with a user named 'pulp' added
So in order to replace the vagrant user with a pulp user, we'll have to update the vagrant box image. I'm opening another task to do this:
https://pulp.plan.io/issues/3065
I'm going with option 1 for now. #3065 will implement option 2.
- Has duplicate Task #2879: Create a 'pulp' user for Pulp3 in the development environment added
- Subject changed from "apache" user used in dev environment, "pulp" user used by ansible galaxy to get rid of "apache" user in dev environment
- Status changed from ASSIGNED to POST
- Sprint/Milestone changed from 45 to 46
- Sprint/Milestone changed from 46 to 47
- Status changed from POST to MODIFIED
- Sprint/Milestone deleted (
47)
- Sprint/Milestone set to 3.0.0
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF