search

lmorchard / fossilizer

A static site generator for Mastodon exports
https://lmorchard.github.io/fossilizer/
MIT License
37 stars 1 forks source link

Integrate pagefind into fossilizer? #7

Open lmorchard opened 1 year ago

lmorchard commented 1 year ago

The current easiest way to build search indexes and assets via pagefind is to just run a release binary after fossilizer build.

It would be nice if pagefind were just a built-in part of the fossilizer executable that can be run as part of the build process. Is this feasible?

vielmetti commented 1 year ago

Looks like other people have had the same idea; see these issues

https://github.com/CloudCannon/pagefind/issues/71 https://github.com/CloudCannon/pagefind/issues/72

Looks like @blgw is targeting this for some future 1.0.0 release, date undefined.

bglw commented 1 year ago

👋 Pagefind is getting close to 1.0, date still undefined but in the order of weeks.

The NodeJS API is available on the 1.0 alpha version, and that communication channel could be explored here.

Also, as both projects are Rust, I'm happy to explore a way to integrate the two more directly. As part of the API work, Pagefind now supports running as a service that can be communicated with, so that aspect wouldn't be all that far away from being a usable crate if you want it to be that ingrained.

Let me know your thoughts and I can then have a dabble. (Or if you want to keep them as separate processes, I can help there too)

lmorchard commented 8 months ago

Thinking one of the easiest initial integrations here would be to use a pagefind binary as a service, like the NodeJS API does. That would at least be like following an already-paved path. We'll see how ambitious I feel as I'm starting to blow the dust off this project again 😅

vielmetti commented 5 months ago

Since the last comment here, Pagefind 1.0 (and 1.1.0) is out. worth noting that the 0.2.x fossilizer needs the 1.x pagefind. (I had an old binary lying around and tried it but some options had changed).