stork VS feather

If your content is mostly static, you might want to consider pre-building an index and shipping it as a whole. You could look into something like

* https://stork-search.net/ (Rust/WASM)

* tinysearch: https://github.com/tinysearch/tinysearch (Rust/WASM)

* https://lunrjs.com/ (JS, simple, stable)

* http://elasticlunr.com/ - based on the former, slightly more sophisticated tuning options

Mostly write about Elixir. Check out the search function. It is a rust library run as WASM in the browser (all the right keywords for HN hehe).

My blog: https://victorbjorklund.com/blog

Search library used: https://stork-search.net/

(And yes, I know it is totally overkill to have search when you just got a few articles)

Also another alternative is stork https://stork-search.net/

Stork seems perfect: https://stork-search.net/

It doesn’t do live crawling, so might not be quite what you want, but I built Stork Search (https://stork-search.net) to solve full-text search for static sites.

Today, you’d run a binary as part of a site’s build or deploy process, feeding in the input files. It generates a search index which you deploy alongside your site. The project’s JS library will load that index and turn it into a client-side interactive search interface.

I’d be curious to see if this sounds interesting or workable for you - you mentioned that you don’t want to host your own index, but does that change if “hosting the index” feels similar to hosting an image, instead of spinning up a server?

I’d be interested in building a paid addition that will crawl your site & host the index - you’re probably the 2nd person I’ve seen with that suggestion. Please let me know if you’d be interested in being a beta user.

You can index your crawl data with StorkSearch[0] then use its js interface for search.

[0]https://stork-search.net/

stork: a fast web search made for static sites

There seems to be an open issue regarding this hopefully it is resolved soon.

Server side: - https://github.com/feather-rs/feather - https://github.com/valence-rs/valence

- What server software or framework to use. Ideally, if you dont need too much vanilla features (world generation, all mobs & items implemented, etc), I'd use something lightweight that is not based off of the vanilla server software. There are a few projects like this on github, including: https://github.com/Minestom/Minestom , https://github.com/feather-rs/feather , https://github.com/KryptonMC/Krypton , https://github.com/df-mc/dragonfly (bedrock). Which one you use will probably depend mostly on your preference. - You will need a way to store data separate from the servers. A database like postgres should work. There are a lot of different databases tho!

There has been some work... feather mc server and piston's hematite client This client also seems to be in active development: Leafish

There is the feather port of Minecraft server. Lacking a gui but the serve could easily reach parity with some community help

As far as your enum idea goes, I don't directly see a place for storing chunk data in an enum (in the way that you would with Some(T). But, totally OK to store your block types that way (as feather-rs does)

The insight contributors chart is usually a good clue. It’s not perfect because it only shows the main branch configured in GitHub and some project haven’t merged to main in years.

Still, it’s good to see how many real contributors a project has, and how active they are over time.

https://github.com/feather-rs/feather/graphs/contributors

In a similar vein, there is also a Rust-based Minecraft server implementation:

https://github.com/feather-rs/feather

I think feather's plugin system is pretty cool