-
Notifications
You must be signed in to change notification settings - Fork 9
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
Watch folders for new/changed/removed photos #73
Comments
To start, would you accept a simple This would be similar to hitting "rescan" in the UI, but could be run periodically (or on first import of a bunch of folders). |
Sure! That's a good idea! Do you think it makes sense to be able to specify any folder even if it's not part of a collection? Should you be able to specify a collection in addition/instead? (A collection can consist of multiple folders) |
Was this ever added? I was looking for an auto refresh or auto scan feature so I don't have to keep doing it manually. Would like to be able to enable it by default using a environment option if possible. Using docker. |
No, not yet, but it's a good idea still! I just haven't gotten around to adding it :) I'm thinking of being able to configure it in the config yaml, maybe globally and per collection. Could be a simple syntax of defining an interval, but could also be crontab syntax. What do you think? |
Is your feature request related to a problem? Please describe.
Actually using the app in day-to-day life is not a great experience. You have to rescan all the time, which can take forever. If you haven't rescanned in a while, the newly added photos can also take minutes to hours to finish indexing. Additionally, there are a bunch of caches that aren't invalidated when scanning, even if you refresh the page, which seems broken and is very annoying.
Describe the solution you'd like
Describe alternatives you've considered
Improving the caching part without adding watch.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: