On Thu, Jul 16, 2020 at 02:56:08PM -0500, Brendan Early wrote:
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.
Yeah, and msuchy (and others) have been working on:
My point is that we shouldn't have 2 groups working on the replacement,
that seems like it's taking time from one group we don't decide to use
the app from. Or is there a possibily to merge the two apps or split the
functionality up so both are complementary?
On 7/16/20 12:06 PM, Kevin Fenzi wrote:
> So, I think we have two groups approaching a replacement app for
> 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?
> infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines