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
Every Coldsweat installation could generate a feed for its status information. Such feed would include:
Feeds disabled by the system due to many errors
Fetch results
This is not as straightforward as one may think. This imply one of these approaches:
Keep an history of events, a sort of log in a separate database table. Such table is queried every time such feed is requested. We can take the last 10 events/last week to be exposed.
Save an atom feed on disk after each status update. Such feed need to be read from disk, parsed, probably trimmed and updated on request.
The text was updated successfully, but these errors were encountered:
Another simpler solution would be to synthesize a new entry when a feed is disabled. This way user will be notified in the feed itself, without any additional effort from her part and without exposing subscribed feeds information outside Coldsweat.
passiomatic
changed the title
Publish a feed for Coldsweat status messages and errors
Publish a feed or custom entries for Coldsweat fetcher status
Jul 3, 2014
Every Coldsweat installation could generate a feed for its status information. Such feed would include:
This is not as straightforward as one may think. This imply one of these approaches:
The text was updated successfully, but these errors were encountered: