Actions
Story #4044
closedAs a user, I can specify a base_path and a relative_path for a Distribution
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Quarter:
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/'.
Actions