New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document using memdown #464
Comments
Added stuff from tests, but need to make a working example to make it accurate. |
Make an extra version of the demo that uses memdown. Got it working over at designing-with-search-data. |
Have something working over at |
This is now (briefly) documented here -> https://github.com/fergiemcdowall/search-index/blob/master/docs/FAQ.md#can-i-use-another-backend-like-mysql-or-redis Does it make sense or is it too cryptic? |
I think it makes sense. Will try |
Is there any working sample how to initialize a redis store with search-index? I am trying to connect to a Redis server on Upstash. |
I could connect to the Redis instance:
but always gets the following error:
|
Can you get any reads and writes to work with |
I did not try that yet. I would like to run search-index as a serverless function. Currently I have deployed it as a Google Cloud function. It works fine, except that in case the function instance is killed the data in tmp dir is lost. Do you have any suggestions how to persist the data in search-index efficiently in a serverless function? Would Redis suitable? |
It works with levelup + redisdown.
Console log: name=levelup |
Hmm- interesting. I will keep this open as a bug for just now, and look into it when I have time. @tonprince Please keep us posted if you find a solution! |
Finally I moved the search-index to compute engine instance, with backup and restore logic from/to Cloud storage. It works like a charm. It uses the standard write logic to file system. |
Great to hear @tonprince ! 🎉🚀 |
Test first
The text was updated successfully, but these errors were encountered: