feed:process
Processes the itch.io feed to discover and update game information automatically.
Overview
This command monitors the itch.io public feed for game updates and processes new events to keep the database synchronized with the latest game information. It includes built-in duplicate detection and retry logic for robust operation.
Key Features: Automatic discovery, duplicate prevention, rate limit handling, comprehensive logging.
Usage
Options
This command has no specific options - it processes the feed automatically using configured settings.
Processing Logic
The command follows this workflow:
Fetches latest feed events from itch.io's public feed
Checks processed events table to avoid duplicate processing
Stops at first already-processed event to prevent reprocessing
Processes new events in chronological order
Updates game information based on event data
Records processed events to prevent future duplicates
Examples
Processes all new events from the itch.io feed since the last run.
Shows detailed processing information including event details and API calls.
Only shows errors, useful for automated/scheduled execution.
When to Use
Recommended Usage Scenarios
Scheduled automatic execution (recommended: every 15-30 minutes)
Manual execution after extended downtime
Testing feed processing after configuration changes
Recovering from failed automated runs
Processing Behavior
The feed processor treats all events uniformly - it doesn't differentiate between event types. For every feed event:
Condition | Action Taken | Data Updated |
|---|---|---|
Game exists in database | Refresh version information | Version details, download links, platform support |
Game not in database | Skip event | None |
Error Handling
The command includes comprehensive error handling:
Rate Limiting: Automatic retry with exponential backoff
API Failures: Retry logic for temporary network issues
Duplicate Detection: Prevents reprocessing of already-handled events
Data Validation: Ensures feed data integrity before processing
Monitoring
Monitor the following during feed processing:
Events processed count - Should match expected feed activity
API rate limit status - Watch for 429 responses
Processing time - Longer times may indicate API issues
Error rates - High error rates suggest configuration problems
Processing Flow
This diagram shows the detailed flow of feed processing:
Related Commands
games:refresh - Manual game information refresh
games:refresh-feedless - Update games not in feed