New poseidon server suggestions

[stschiff]

Once we've added the html branch with the new archive explorer, here are some suggestions for improvement:

• It would be great for the front pages to list a short sections with "newest packages" or "most recent package updates" or so.
• Alternatively, or in addition to that, it would be nice to show the "last-modified" date for each package in the table
• Lastly, it would be great to have the table dynamic, and sortable.

This is just a wishlist, feel free to ignore for now.

[nevrome]

• The front page should maybe also feature some dashboard-like visualizations (?) about the state of each archive

[nevrome]

• The front page should include a powerful full text search. I think the best way to implement this would be a custom search index system in trident (maybe like this). This could then also support a subcommand trident search to search locally and --remotely.

[stschiff]

Hmm, I'm intrigued. But would this search index be stored on disk somewhere, and trident reads it? How would this work for both remote and local?

[nevrome]

It depends a bit on how long the construction of the index takes. Maybe doing it live is impractical for a trident search command. This could be solved by pre-computing and storing it in something like cbor. I use that already pretty successfully for another Haskell project. It's a very efficient binary representation that can be used directly for Haskell data structures.

The server could certainly hold it in memory. It's running permanently anyway. So there would be a new API that takes and responds to search queries. And that could be used by a trident search --remote.

I'm dreaming a bit here. No idea, when I will have the time to implement this.