Hi.
I've deployed the static website to GitHub Pages at https://abitrolly.github.io/fedora-packages-static/ The search doesn't work, and there is no index to browse, so it is not very useful. Looks like the search is supposed to be Solr, which is not static.
On 12/11/20 12:21 AM, Anatoli Babenia wrote:
I've deployed the static website to GitHub Pages at https://abitrolly.github.io/fedora-packages-static/ The search doesn't work, and there is no index to browse, so it is not very useful.
If you'd like to see the prototype container with working search:
1. Create a pod using podman (ports 8983 for solr admin and 80 for -packages-static) 2. Create a solr container in the pod 3. Create a core in solr with the name `packages` configured with the files in the solr directory 4. Build the dockerfile and add it to the pod. It will serve files after the initial sync
There is an index at https://abitrolly.github.io/fedora-packages-static/sitemap.xml (for search engines, still needs a config env var for base URI)
Looks like the search is supposed to be Solr, which is not static.
Yes, unfortunately the only way to handle search is dynamic. Either via JS that locally handles search or an external service. Currently, I have a small (~40 line) uWSGI script that acts as a proxy for Solr and formats results. The reason I went with this approach is that it keeps JS optional, you get the benefits of a full search platform, and it will not slow down the browser during a query.
How hard is to swap Solr search engine backend to client side JS search? Are there any fast client side JS search engines?
If no-JS navigation is important, maybe it is possible to add clickable index for all packages under the search form?
I added CI job for GitHub Pages, but of course it is impossible to host Solr backend there https://github.com/abitrolly/fedora-packages-static
On 2/1/21 10:07 AM, Anatoli Babenia wrote:
How hard is to swap Solr search engine backend to client side JS search? Are there any fast client side JS search engines?
Probably not too hard, I have not researched what libraries are available. I would not try to use client side search for anything outside of just searching package names due to potential performance and quality issues.
If no-JS navigation is important, maybe it is possible to add clickable index for all packages under the search form?
No-JS is a goal. There used to be an index before the sitemap, it should be easy to pull that out of the commit history.
I added CI job for GitHub Pages, but of course it is impossible to host Solr backend there https://github.com/abitrolly/fedora-packages-static _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@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 List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
infrastructure@lists.fedoraproject.org
-
Anatoli Babenia -
Brendan Early