Story #4044
closed
As a user, I can specify a base_path and a relative_path for a Distribution
0%
Description
Problem: Distributions have to be served at /pulp/content/<base_path>/
Content types that need to be hosted outside the /pulp/content/ URL space cannot use the Distribution to make a publication available at some URL.
Solution: Add an additional 'relative_path' field to the Distribution. The 'base_path' will default to '/pulp/content/', but the user would be allowed to set it to whatever value is needed by the plugin that is serving the Distribution. The 'relative_path' would serve the role of the 'base_path' now.
The content app would need to be updated to only look through distributions that have the 'base_path' set to '/pulp/content/'.
Updated by bmbouter over 5 years ago
This looks good to me, but that will only work if those URLs are being forwarded by the webserver to Pulp's WSGI app serving those viewsets. I think that motivates Pulp being deployed at / and not nested deeper in the urlspace. Does that sound right?
FYI, we talk some about this here: https://docs.pulpproject.org/en/3.0/nightly/overview/components/webserver.html#wsgi-application
Updated by daviddavis over 5 years ago
I think that motivates Pulp being deployed at / and not nested deeper in the urlspace. Does that sound right?
Will that work for installations like Katello where there are multiple apps running alongside pulp on the same box?
Updated by bmbouter over 5 years ago
It will work. They will use vhost with either SNI serving it up on another port via localhost.
Updated by dkliban@redhat.com over 5 years ago
- Status changed from NEW to CLOSED - NOTABUG
Decided that this is not worth implementing just for 1 plugin to use. If we decide there is value in the future, we can revisit.
.