Open fao89 opened 2 years ago
Author: mdepaulo@redhat.com (mdepaulo@redhat.com)
Redmine Issue: 6130, https://pulp.plan.io/issues/6130
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
django-admin runserver
The agreed upon solution is to turn it into a subcommand of pulpcore-manager
Docs updates will be required for this change too.
Author: mdepaulo@redhat.com (mdepaulo@redhat.com)
Redmine Issue: 6130, https://pulp.plan.io/issues/6130
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 runserverallows 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/4218The agreed upon solution is to turn it into a subcommand of pulpcore-manager
Docs updates will be required for this change too.