You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 8, 2024. It is now read-only.
While reading through the documentation I came across this section
This seems very brittle and transient. I think removing this as a hidden API call, and making this a configuration option for the feed in '../Hippocampe/core/conf/feeds' might be a more useful feature since thats where we configure the feeds we're going to download.
Keeping the API call + allowing it configurable via feed configurations also seems solid.
The text was updated successfully, but these errors were encountered:
Yes. I think creating an option in core/conf/feeds/<feed>.conf which allows you to specify a variable that lets you set how often a feed is redownloaded (Something like sync : 12h ).
We then would calculate the duration between feed's lastQuery field and time of indexation.
Compare the duration with sync value and depending on the result update or not.
We sure could implement that.
First we need to figure out whether we keep the sync value AND the API call or only one of these two...
Will +1 this as some feeds are actually updated on an hourly basis, some 24 hours, some unknown. Having more aggressive pulls for faster-updated feeds makes a lot of sense.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature Request
While reading through the documentation I came across this section
This seems very brittle and transient. I think removing this as a hidden API call, and making this a configuration option for the feed in '../Hippocampe/core/conf/feeds' might be a more useful feature since thats where we configure the feeds we're going to download.
Keeping the API call + allowing it configurable via feed configurations also seems solid.
The text was updated successfully, but these errors were encountered: