-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[FEATURE_REQUEST] SQL Backend #836
Comments
+1 I don't know if database storage will fix this issue but I have about ~100+ links and have the same problem, search is unusably slow and clicking on links from the search results does not work, I have to use find in the browser. |
Right now I'm redoing the config process, re #799, but still YAML-based. Using a single file for configuration was the main point of Dashy, so it sounds like in your use case a different dashboard app might fit you better - here's some alternatives. |
This issue has gone 6 weeks without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days. |
This issue was automatically closed because it has been stalled for over 6 weeks with no activity. |
This issue was answered and can be closed. Thank you. |
Is your feature request related to a problem? If so, please describe.
Looking to implement dashy with a large amount of links. Currently have a setup with about 150+ links. Once it starts to get this large the search feature tends to lag and you lose the ability to click on the results once you type in the search field. Would it be possible to integrate with an SQL database to speed up the search results and keep adding links.
If I missed this in the documentation or this has already been requested I apologize. Thank you for your time and hard work.
Describe the solution you'd like
Adding an SQL database for the URL links to speed up search results.
Priority
Low (Nice-to-have)
Is this something you would be keen to implement
No
The text was updated successfully, but these errors were encountered: