Kerollmops

8 ms·

61.
by Kerollmops 7y ago
I understand what you mean but is it for a specific usage of a search engine? I was thinking that this kind of time-restricted tokens could also be managed by the nginx instance, our engine doesn't support that for the time being.
62.
by Kerollmops 7y ago
Go on and try MeiliSearch, 50k documents are easily handled by the engine and with not much RAM usage. It will take you something like 10 minutes to start and populate MeiliSearch, you will be able to test it just by going to the server HTT
63.
by Kerollmops 7y ago
Currently we think this kind of security can be enabled by a simple nginx setup, allowing autorefesh of certificates easily (e.g. certbot). But in the future we will probably handle that in the engine itself.
64.
by Kerollmops 7y ago
Yes, there is, you can find all clients on this documentation page: https://docs.meilisearch.com/resources/sdks.html Note that we are reworking the js library and there will probably be React integration too!
65.
by Kerollmops 7y ago
MeiliSearch is "zero-config" compared to ElasticSearch in terms of setup to make it work for end-user instant and relevant search engine. Our engine follows the Algolia engine in terms of typo-tolerance, relevancy, and speed. Here
66.
by Kerollmops 7y ago
The current API key system is a simple and temporary solution. We will work on a more feature-full API key system including the one you are talking about. This is on our roadmap IIRC.
67.
by Kerollmops 10y ago
It remind me of the FTL OST Good for programming too !