Issue #6130
closed
Users have a tendency to run /usr/local/bin/pulp-content in production
Description
Ticket moved to GitHub: "pulp/pulpcore/1866":https://github.com/pulp/pulpcore/issues/1866
The ansible galaxy team was running pulp-content in production by running the /usr/local/bin/pulp-content script: https://github.com/pulp/pulpcore/blob/master/bin/pulp-content
However, this script is not meant to be run in production, only for quickly launching pulp-content like django-admin runserver allows for pulp-api. Users should use gunicorn like the systemd unit and the containers specify in production.
https://github.com/pulp/pulpcore/commit/9c36548f4b1f264ea1b835f49c077b67cf6d0d43
https://pulp.plan.io/issues/4218
The agreed upon solution is to turn it into a subcommand of pulpcore-manager
Docs updates will be required for this change too.
Related issues
.