make repo index listings more readable in a web browser (easy fix)
By default (thanks Apache...), package listings in repos are really not that useful via a web browser because the default is to truncate filenames after the first 20 bytes.
I easily fixed this globally on my Pulp server by augmenting the following line of /etc/httpd/conf.d/autoindex.conf:
- IndexOptions FancyIndexing HTMLTable VersionSort
+ IndexOptions FancyIndexing HTMLTable VersionSort NameWidth=*
...but this can be fixed in the Pulp installation by adding that option to the right places (up to you guys specifically which) in the pulp_rpm.conf or other pulp-provided files. Attached is a visual example of how much nicer listings are without truncation.
#1 Updated by firstname.lastname@example.org over 4 years ago
As of 2.8.0 the way the index gets generated had to move from Apache to a Python WSGI application we control. It does not truncate file names, but it doesn't contain size or modification information for files (one step forward, two back...)
Given that, do you want to use this issue to track feature parity with Apache's index, or close it?
#3 Updated by kfiresmith over 3 years ago
I would like to work on this issue. Is this scenario still valid ?
I would still welcome this enhancement. I am running 2.10 currently and noticed that things like the modify date of files in the index no longer show up, but I'm not sure when that went away or why.
#4 Updated by bmbouter over 3 years ago
@akasurde we would welcome this contribution. Getting a working development environment  is probably the first step. Also we have a developer mailing list for dev questions too. Learn more about that that here.
#7 Updated by bmbouter over 1 year ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
Please register to edit this issue