[docs-only] Use correct envvar caching names in service readme's

This commit is contained in:
mmattel
2023-05-16 15:54:37 +02:00
parent 6bfbc698f2
commit edc4c4bb42
5 changed files with 7 additions and 8 deletions
+1 -1
View File
@@ -18,7 +18,7 @@ When all postprocessing steps have completed successfully, the file will be made
The `postprocessing` service needs to store some metadata about uploads to be able to orchestrate post-processing. When running in single binary mode, the default in-memory implementation will be just fine. In distributed deployments it is recommended to use a persistent store, see below for more details.
The `postprocessing` service stores its metadata via the configured store in `POSTPROCESSING_STORE_TYPE`. Possible stores are:
The `postprocessing` service stores its metadata via the configured store in `POSTPROCESSING_STORE`. Possible stores are:
- `memory`: Basic in-memory store and the default.
- `ocmem`: Advanced in-memory store allowing max size.
- `redis`: Stores data in a configured Redis cluster.