The official GitHub page for Discourse says “ We use Redis as a cache and for transient data. ”. But Sidekiq, which is a part of Discourse, says “ Many people use Redis as a cache but it’s important that Sidekiq be run against a Redis instance that is not configured as a cache but as a persistent…

In general we try to avoid Redis flushes, but it’s not completely the end of the world if it does get flushed. Worst case, some emails might not get sent such as password resets and users will need to re-request.

¿Debería Redis configurarse como servidor de caché o no?

Instalación

Falco (Falco) 10 Abril, 2016 23:35 9

3 Me gusta

Tema		Respuestas	Vistas
What does Discourse use Redis for? Dev	5	3270	18 Agosto 2022
Sidekiq not running. Sidekiq heartbeat test failed, restarting Installation unsupported-install	15	2746	10 Junio 2020
Can I install Discourse with my own Redis and Postgres? Installation	5	2064	3 Febrero 2021
Problems with installing discourse on heroku(mostly a redis error) Installation	12	3919	15 Julio 2015
Using Discourse in traditional server Installation	3	1041	21 Febrero 2016

¿Debería Redis configurarse como servidor de caché o no?

Temas relacionados