There are two points where the caching service comes into play:
1. when the frontend requests the cover for a comic,
2. when the frontend requests the content for a specific page out of a
comic, and
3. when the frontend requests the contents for a page directly.
in each of those cases, the backend grabs the page's details out of the
database, converts the page's hash into a path and then peeks into the
caching directory to see if a file exists. If it does, it returns the
contents of the file, which is the image. Otherwise, it pulls the file out
of the archive, creates that caching file, then returns the contents.
On Sat, Dec 14, 2019 at 8:32 PM bareheiny <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
As per subject, what triggers the generation of the cove caches?
