Hi,
Timothée and I are working on fedora-packages-static. It's a lot
simpler than the old packages app, it just generates static files
that you can serve. The old packages app was missing packages and
would time out if an external service took too long to respond.
This approach eliminates those problems by not having the web
server do that work on demand. Because these are just static
files, search will need to be managed by something else (E.g.
YaCy, Algolia). I have generated an example page and put a link
below.
Example:
https://mymindstorm.fedorapeople.org/pkgs-demo/pkgs/numix-icon-theme-square/
Pagure: https://pagure.io/fedora-packages-static
--
Brendan Early
So, I think we have two groups approaching a replacement app for packages? Can we perhaps decide which way we want to go and look at deploying something soon? This has been more important since we didn't move the old broken packages app from the old datacenter and people keep asking about it. We could wait until we have staging back, but I don't think we need to wait for that to decide what we want to do here? Thoughts? kevin
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx