Move temporary reading history to a separate Redis instance

Description

Similar to where we move hit count data out of REDIS_GENERAL and into a separate Redis instance, we want to do the same for reading data.

  • Create new configuration REDIS_READINGS; update reading code to use it; update tests to flush it.

  • Start an extra Redis instance for REDIS_READINGS in Travis; use an existing Redis instance for it in Codeship.

  • Remove reading_tasks.rake and move the task to resque-scheduler, with a schedule of 55 * * * *.

How to test:

  • Visit some works (once or multiple times), wait for the scheduled task to run, then check that your reading history is updated as expected (view count up, last visited time changes).

Post-deploy:

  • Run rake readings:to_database one last time on an old copy of the code (like ), to move all data from the old Redis instance to the database.

Assignee

Unassigned

Reporter

redsummernight

Roadmap

Reading History

Priority

Medium

Affects versions

Fix versions

None

Components

BackEnd

Difficulty

Medium

Milestone

Internal 0.9
Configure