A static tree on the left can be created quite easily (apache supports full HTML headers/footers) plus it will allow to better integrate the look of resources with the main project website. We can even create a script that will parse the directory tree and compose an XML file that the browser can then draw as a tree. Will try it out on the staging server and share the results here

what actually seems to be causing issues is the fact the we have a server-side script that makes the index pages look more complex then a list of links to files. This is what causing link scraping tols like repoman fail when trying to parse them.

, , could you provide a short summary of what repoman would tolerate on index pages?

I think we may have to resort to doing some things on the client side, in order to make pages yielded from the server rather simple and only display directory trees to real web browsers that parse HTML.

BTW, we may not require a full directory tree. A somewhat static navigation bar that lists the various repositories in semantic manner (E.g. oVirt releases, older ovirt releases, nightly snapshots) may be sufficient and actually allow us to hid some of the more confusing stuff like user repos.

Apache directory index listing can be made pretty quite easily by adding headers, footers, CSS styles and replacing file type images. What this doesn't have is directory trees and as discussed in this seems like a feature that is a must. To have trees we need to have some kind of server-side script, I'll check what is available and report here.

I'm not sure it's only repoman, as I also recall a few times seeing outdated info via the PHP interface ( which I verified by visiting plain.resources.ovirt.org ), so either it was a caching issue on the browser or a bug in the PHP, its another issue that justifies removing this app. ( along with the potential security implications )

So to summarize, I agree we should improve the default HTML page resources.ovirt.org shows, and possibly brand it with oVirt colors and logo,
and then remove the PHP app.

Ah,.. right so its ONLY a repoman issue.