mirror/opencloud
1
0 Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-10-23 06:39:13 -04:00
Code Issues Packages Projects Releases Wiki Activity

[docs-only] Fixing the service name in the text used in readme.md

Browse Source
This commit is contained in:
mmattel committed 2023-04-04 12:15:59 +02:00
1 parent b9257a6a24
commit 3c35b95ee2
3 files changed
+3 -3
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

services/gateway/README.md
+1 -1
View File
@@ -11,4 +11,4 @@ The `gateway` service can use a configured store via `GATEWAY_CACHE_STORE`. Poss
1. Note that in-memory stores are by nature not reboot persistent.
2. Though usually not necessary, a database name and a database table can be configured for event stores if the event store supports this. Generally not applicapable for stores of type `in-memory`. These settings are blank by default which means that the standard settings of the configured store applies.
3. The proxy service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances.
3. The gateway service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances.
services/graph/README.md
+1 -1
View File
@@ -27,5 +27,5 @@ The `graph` service can use a configured store via `GRAPH_STORE_TYPE`. Possible
1. Note that in-memory stores are by nature not reboot persistent.
2. Though usually not necessary, a database name and a database table can be configured for event stores if the event store supports this. Generally not applicapable for stores of type `in-memory`. These settings are blank by default which means that the standard settings of the configured store applies.
3. The proxy service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances.
3. The graph service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances.
4. When using `redis-sentinel`, the Redis master to use is configured via `GRAPH_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
services/ocs/README.md
+1 -1
View File
@@ -15,5 +15,5 @@ The `ocs` service can use a configured store via `OCS_STORE_TYPE`. Possible stor
1. Note that in-memory stores are by nature not reboot persistent.
2. Though usually not necessary, a database name and a database table can be configured for event stores if the event store supports this. Generally not applicapable for stores of type `in-memory`. These settings are blank by default which means that the standard settings of the configured store applies.
3. The proxy service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances.
3. The ocs service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances.
4. When using `redis-sentinel`, the Redis master to use is configured via `OCS_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.