Actions
Story #4180
closed
As a user, Pulp will serve Pulp's static content natively without extra configuration
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Sprint 47
Quarter:
Description
This was originally discussed on this mailing list thread:
https://www.redhat.com/archives/pulp-dev/2018-October/msg00034.html
Problem¶
Users have to deploy a webserver and configure it if they want to deploy Pulp with any static media. This is a barrier to usage.
Solution¶
Adopt "whitenoise" as a dependency and have Pulp auto-configured to collect and serve static media with it. The static media can line in a place like: /var/lib/pulp/static/
Actions
.
Problem: static files are not available on user installs
Solution: collect static files before releasing to PyPI
This patch adds the 'whitenoise' middleware that serves static content for Pulp. 'whitenoise' is configured to serve static content found in pulpcore/app/static directory. This means that after installing pulp, the user will need to run the 'pulp-manager collectstatic' command to get all the static content into the directory.
closes #4180 https://pulp.plan.io/issues/4180