ami/tl-vikunja
1
0
Fork 0
Code Activity

chore: remove cache options

Browse Source 
Cache was not working correctly, added more complexity and actually made response times slower. Because of this, I'm removing all cache options until we figure out a better solution.

Resolves https://kolaente.dev/vikunja/api/issues/1496
Resolves https://kolaente.dev/vikunja/api/issues/907
This commit is contained in:
kolaente
2023-06-08 17:05:36 +02:00
parent 72e0e22152
commit d83e3a0a03
10 changed files with 0 additions and 156 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
docs/content/doc/setup/config.md
View File

@ -494,47 +494,6 @@ Full path: `database.tls`
Environment path: `VIKUNJA_DATABASE_TLS`
---
## cache
### enabled
If cache is enabled or not
Default: `false`
Full path: `cache.enabled`
Environment path: `VIKUNJA_CACHE_ENABLED`
### type
Cache type. Possible values are "keyvalue", "memory" or "redis".
When choosing "keyvalue" this setting follows the one configured in the "keyvalue" section.
When choosing "redis" you will need to configure the redis connection separately.
Default: `keyvalue`
Full path: `cache.type`
Environment path: `VIKUNJA_CACHE_TYPE`
### maxelementsize
When using memory this defines the maximum size an element can take
Default: `1000`
Full path: `cache.maxelementsize`
Environment path: `VIKUNJA_CACHE_MAXELEMENTSIZE`
---
## redis