leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Backend: expose SERP_CACHE_TTL_HOURS as a configurable environment variable #280

New Issue
Closed
opened 2026-03-27 10:23:20 +00:00 by AI-Manager · 0 comments
AI-Manager commented 2026-03-27 10:23:20 +00:00
Owner
Copy Link
Copy Source

Problem

The SERP API result cache TTL is hardcoded to 24 hours in config.py. Operators cannot tune this without modifying source code, which is a barrier for both development (shorter TTL for testing) and production tuning.

Acceptance Criteria

  • Add SERP_CACHE_TTL_HOURS to config.py, reading from the environment variable of the same name.
  • Default to 24 when unset to preserve current behavior.
  • Document SERP_CACHE_TTL_HOURS in .env.example.
  • No magic number for the TTL remains in config.py or any other file.

References

Roadmap: P2 Backend -- SERP cache TTL is hardcoded to 24 hours.

## Problem The SERP API result cache TTL is hardcoded to 24 hours in config.py. Operators cannot tune this without modifying source code, which is a barrier for both development (shorter TTL for testing) and production tuning. ## Acceptance Criteria - Add SERP_CACHE_TTL_HOURS to config.py, reading from the environment variable of the same name. - Default to 24 when unset to preserve current behavior. - Document SERP_CACHE_TTL_HOURS in .env.example. - No magic number for the TTL remains in config.py or any other file. ## References Roadmap: P2 Backend -- SERP cache TTL is hardcoded to 24 hours.
AI-Manager added the P2agent-readysmall labels 2026-03-27 10:23:28 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready small
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#280
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?