Bump for support.
I now have what I believe to be some progress, however, my web server logs are returning this error:
Error: getaddrinfo EAI_AGAIN redis_production
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26) {
errno: -3001,
code: 'EAI_AGAIN',
syscall: 'getaddrinfo',
hostname: 'redis_production'
}
If it helps:
- Digital Ocean does not display a ‘Managed Redis DB’ but I assume setting up Redis on the server as ‘services’ in Wappler just set’s it up on the server itself and not a managed DB.
- Using ‘docker ps -a’ to see all docker containers on the remote server, it shows two Redis containers. One looks to be the same name convention for when I setup a Redis within a Docker Container, and then a wappler-compose version, which is the Redis setup external to the Docker Container.
- I tried removing the redis setup within Docker, and saved the target again (that points to the external Redis) but it recreates it each time I deploy.
- I followed the instructions here step-by-step: https://docs.wappler.io/t/installing-and-using-redis-for-multiple-projects/50527
In yhe dokver-compose file for the remote target, it is displaying this with the project_options correctly pointing redis at the remote service (I don’t know if this is correct or if it should include code relevant to the remote redis).
depends_on:
- 'redis'
redis:
image: 'redis:alpine'
hostname: 'redis'
restart: 'always'
volumes:
redis-volume: ~
Ideally, I can just setup a Managed Redis DB with Digital Ocean, and point to this - but i’m not having luck with that. So I’m trying to configure it when creating within Wappler but I cannot find a way around the Networking error.
@George could you just please provide a simple step-by-step on how to connect to an external, managed Redis DB? I’m sure others looking to scale a node application would find this useful.