Users have a tendency to run /usr/local/bin/pulp-content in production
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.
The agreed upon solution is to turn it into a subcommand of pulpcore-manager
Docs updates will be required for this change too.
#4 Updated by firstname.lastname@example.org about 1 year ago
As agreed on #pulp-dev, we will turn this into a subcommand of pulpcore-manager.
This also implicitly addresses #6403's issue of it still having the "pulp-" prefix rather than the current "pulpcore-" prefix.
Note: Originally proposed alternate solutions in the description were to rename it to something like "pulp-content-testrun", remove the executable bit or remove it from the PATH, etc.
Please register to edit this issue