Repository navigation
Use Solid Cache for the production Rails cache - #345
thomasklemm wants to merge 1 commit into
Conversation
|
Reviewed the updated GPT on behalf of DHH |
|
Small fix in Production Generated by Claude Code |
9bea7be to
8c8551b
Compare
Rails.cache moves from Redis to Solid Cache, in its own SQLite database that db:prepare creates from db/cache_schema.rb. Entries aren't copied, so the cache starts cold after the upgrade. The cache database keeps SQLite's own WAL checkpoints, since the checkpoint contender only checkpoints the primary database. The restore hook deletes it: a copy taken from a running volume can be torn, and the cache refills on demand. The HTTP benchmark prepares the databases before starting Puma, so a seed made before a new database or migration still boots.
8c8551b to
0605b38
Compare
Moves the production
Rails.cachefrom Redis to Solid Cache, in its own SQLite database thatdb:preparecreates. It's the first of three steps toward running Campfire without Redis: #346 moves the jobs and #347 Action Cable.Entries aren't copied, so the cache starts cold after the upgrade. The cache database keeps SQLite's own WAL checkpoints, since the checkpoint contender only checkpoints the primary database. The restore hook deletes it rather than keep a copy taken from a running volume; it refills on demand. The HTTP benchmark now prepares the databases before starting Puma, so seeds made before a new database still boot.