What's Changed
- Add gluetun configuration example by @mgdigital in #83
- Downgrade asynqmon by @mgdigital in #92
- Reduce aggregations in web UI by @mgdigital in #87 (Fix #85):
- Accurate counts in the web UI will only be shown for the top-level filters; when deep-filtering, the counts will show a less than or equal sign:
≤, indicating the number is a "maximum possible" rather than an accurate count; I'm still not sure about the UX aspect of showing the≤which could be confusing if you're not sure what it means, but I figured it's better than showing nothing at all - open to suggestions! - A background process keeps the in-memory query cache warm for the top-level aggregations (by default every 10 minutes), allowing them to be served instantly
- The query cache TTL has been increased to 20 minutes; improved performance is preferable to seeing the most up-to-date information
- Pagination has been refactored to account for not knowing the total number of pages; internally the search engine will request 1 more item than it needs to know if there's a next page to advance to
- Some general refactoring of the web app
- Accurate counts in the web UI will only be shown for the top-level filters; when deep-filtering, the counts will show a less than or equal sign:
Full Changelog: v0.3.1...v0.4.0