Caddy is great. But it has some of the worst documentation I’ve ever seen. It’s so messy and unstructured.
One example: it was almost impossible to find instructions on where to actually put the damn Caddyfile. After reading the docs 10 minutes, I gave up and resorted to Google site search.
This page explains all that: https://caddyserver.com/docs/running. Ultimately it depends how you installed Caddy and how you're running it (Docker vs Systemd vs directly via CLI, etc).
Thank you for Meilisearch. I've been using it for https://www.comparedial.com/ (phone contract comparison website) for over a year with great results. Well done on the funding.
In a hypothetical situation where energy is not a limitation, would it be possible to generate the same amount of water that we currently use in the world only from atmospheric water generators?
If energy is not limitation, you can do almost anything you want, like making diamond, water and microprocessors from grass clippings. The water we currently use in the world IS coming in from air, it's called rain. There are rivers and lakes full of it. Precipitating it would just make it rain a little less.
'You Don't Know JS' by Kyle Simpson. A series of books that are a must read for any JavaScript developer. They are available for free on GitHub or you can purchase a retail version. He's working on a second edition right now.
Kanye West is going to bring Yeezy manufacturing back to the US. Here's an interview from 2 years ago that is very insightful: https://youtu.be/ihfG8qlhW04?t=760
It's ridiculously easy to use and has faceted search for my needs. However, there are some limitations so I have to use it in combination with redis, but the developers have a roadmap to fix these problems.
Synchronising with MeiliSearch is a bit of an effort because of the following limitations:
* When filtering by facet, it doesn't provide count for disjunctive facets
* No sort by
* No where clause (less than 50 for example)
To overcome these problems, I rebuild some parts of the database in redis, use code for filtering and query MeiliSearch multiple times for different facet counts.
Both redis and MeiliSearch are ridiculously fast so the performance loss is negligible, but it makes my code quite complex. As soon as the developers add these missing features, I want to simplify my code and only use redis for query caching. Typesense had some of these limitations too, but I'm not sure if that's still the case.
Hi! MeiliSearch product team here! It's super cool to see your feeback!
Concerning the disjunctive count of the facets, we are thinking about it. It is feasible on the client side by making several requests but we are aware that is it not ideal at all from a developer experience point of view. We are still thinking about the best way to solve that case in one of our future iterations!
The sort feature is coming in v0.22 (string and numeric fields) you will be able to easily configure the balance between exhaustivity and relevancy at index level through the positioning of the ranking rules.
I'm not sure I understand the where clause point so I'd love to hear more details!
Thanks for using us and giving us this kind of feedback :)
Our Image Resizing product offers this already. The Images product (what we announced today) will provide most of the features available with Image Resizing with Variants.