Cache: ape cache prune

[NotPeopling2day]

Overview

Eventually the cache database on disk will get rather large and user's should have a way of trimming the file size. We will use a time-based pruning process with on a configurable upper limit to the database file size set in ape-config.yaml.

Specification

• Add last_access timestamp field to all cache tables
• ape cache prune - manual command
• auto pruning w/ opt out ability

Acceptance Criteria

• Max cache file size can be set in ape-config.yaml
• Cache file will not exceed max cache file size
• Oldest records will be removed first
• New records can be added
• No duplicates in the cache

Dependencies

Include links to any open issues that must be resolved before this feature can be implemented.