#How can I check, if Redis REALLY works?
12 messages · Page 1 of 1 (latest)
Thanks for posting! This is a community powered server, so you may or may not get an answer based on available help and expertise. To increase your chances of somebody being able to help you, please help us help you making sure you:
- Adding an explanation of exactly what you're trying to achieve.
- Adding any and all related code or previous attempts.
- Describing the exact issue or error you are facing.
- Posting any screenshots if applicable.
- Reading through https://stackoverflow.com/help/how-to-ask.
When you're done with this thread, please close it. Thanks! ✨
(If you have a support agreement and need help, please contact the core team via email.)
You can use something like https://github.com/RedisInsight/RedisInsight to inspect your redis instance(s).
Thank you, @trail imp ! Would you happen to know how to setup this tool with a local Docker instance? I use these instructions:
https://docs.redis.com/latest/ri/installing/install-docker/
https://collabnix.com/running-redisinsight-using-docker-compose/
and currently have this in my docker-compose.yml:
[...]
networks:
default:
name: dk
services:
dk_database:
image: mariadb:lts
[...]
dk_cache:
image: redis:7.0-alpine
dk_directus:
image: directus/directus:10.5.2
[...]
dk_redisinsight:
image: redislabs/redisinsight:latest
ports:
- "8001:8001"
depends_on:
- dk_database
- dk_cache
volumes:
- ????
An interface opens, but it requires configuration. I do find examples where a volumes parameter is given. But I have no idea what that parameter would be in my case. How can I find that out?
RedisInsight is an intuitive and efficient GUI for Redis, allowing you to interact with your databases and manage your data—with built-in support for the most popular Redis modules. It runs on Windows, macOS, Linux and even can be run as a Docker container and Kubernetes Pods.
Last week, I came across the StackOverflow question around RedisIn...
I had a little bit of success configuring the Redis on that form that pops up on localhost:8001. However, I would rather not have to do that each an every time. Is there a way to persist that connection info?
Also: Why is there no volumes configuration for the cache service in the docker-compose.yml? Would it be possible to define a volumes paramter for the Redis cache there?
@solid quiver Thank you! – Do you happen to know why Directus's configuration section for Redis (in the docker-compose.yml) doesnot use the volumes parameter?
You don't need a volume in general - volumes are for persistent storage.
But if you have a volume, you also need to define the volume, like:
services:
dk_redisinsight:
image: redislabs/redisinsight:latest
ports:
- "8001:8001"
depends_on:
- dk_database
- dk_cache
volumes:
- myvolume
volumes:
myvolume:
Or you can create a volume for the path you are in, like:
services:
dk_redisinsight:
image: redislabs/redisinsight:latest
ports:
- "8001:8001"
depends_on:
- dk_database
- dk_cache
volumes:
- ./myvolume
The last will creat a folder named myvolume in your path.
Mikke is exactly right 🙂 It's no requirement for the cache to be persisted but you can if you want
@solid quiver & @trail imp Thank you very much! I will dig into that and see what happens! Might come back again with more question... 🙂