[FEATURE] Template support for pulp-content
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Hello Pulp team,
first things first: Pulp is an awesome tool for software distribution.
I see that the Jinja template for pulp-content is hardcoded at: https://github.com/pulp/pulpcore/blob/5040c799a05e1fe7f1d090aa97da3571301d4ff2/pulpcore/content/handler.py#L549-L575
Instead of this hardcoded template, I want to customize the content page per Pulp domain. Currently this is only possible by patching the source code. A possible solution would be to have a custom directory with Jinja templates (e.g. which I can mount as docker volume) with the following files:
default.j2domain1.j2domain2.j2
where default.j2 is the default template for all domains or when domains aren't enabled at all.
Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in pulpcore/content/handler.py at the hardcoded Jinja template around lines 549-575, and trace how the content page determines its domain. Define the template lookup and configuration behavior for default.j2 and domain-specific templates, then verify that the default and per-domain pages render as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, content
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100