-
Notifications
You must be signed in to change notification settings - Fork 32
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
Fallback from Algolia search #1449
Comments
The context is: for some customers that won't use our cloud we don't want to setup Algolia or Amazon S3. So we want to be able to deactivate both features. For the files it's already implemented as a setting in the application.yml. The idea is to have a setting too for the search. For the moment, the scope of the issue is to replace the search just for budgets module. We will need to decide what to do in the rest of modules. In budgets it's very easy to replace becaue we have this autocomplete. What you have done looks good to me. |
We will need to decide what to do in the rest of modules.
We don't need to worry about this for the time being.
|
Algolia account shouldn't be mandatory in the budgets module.
When Algolia is not present, use the ES search implemented in the budgets explorer.
The text was updated successfully, but these errors were encountered: