@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.)
hq.recaptime.dev/wiki/Phorge
phorge
phabricator
1@title Managing Caches
2@group config
3
4Discusses Phorge caches and cache management.
5
6Overview
7========
8
9Phorge uses various caches to improve performance, similar to the caches
10a web browser uses to improve web performance.
11
12In particular, blocks of text which are expensive to render (like formatted
13text and syntax highlighted code) are often cached after they're rendered for
14the first time. When they're rendered again, Phorge can read the cache
15instead of recomputing the result.
16
17Because text is cached, you may continue to see the old result even after you
18make certain configuration changes which should affect it. The most common
19example of this is that if you enable syntax highlighting with Pygments, old
20diffs and pastes may not appear highlighted.
21
22You may also run into this issue if you modify existing Remarkup rules or
23develop new ones, or modify other parts of the code that run before the results
24are cached.
25
26Caches will naturally expire over time, so if they aren't causing a problem
27you can just ignore the out of date caches and they'll fix themselves
28eventually (usually within 30 days).
29
30If you don't want to wait, you can purge the caches. This will remove any
31cached data and force Phorge to recompute the results.
32
33Purging Caches
34==============
35
36If you need to purge Phorge's caches, you can use the CLI tool. Run it
37with the `--help` flag to see options:
38
39 phorge/ $ ./bin/cache purge --help
40
41This tool can purge caches in a granular way, but it's normally easiest to
42just purge all of the caches:
43
44 phorge/ $ ./bin/cache purge --all
45
46You can purge caches safely. The data they contain can always be rebuilt from
47other data if Phorge needs it.