Level 43
Did you provision a Elasticache redis cluster?
Apr 17, 2020
9
Level 11
Using redis in your code, in vapor
I have redis set up on my vapor app/environment for caching, but I need to use redis in my code for functionality.
It works locally but when deployed I get errors on my first call to redis and it seems to be in the connection itself.
I assumed the config/environment variables were already set up to use redis, but maybe not.
Has anybody here used redis programmatically on vapor?
Note: I am using phpredis extension and not predis.
Level 11
Yes it is provisioned in Vapor, my vapor.yml has the cache: cachename entry and I see some activity on AWS monitoring (page caching at this point I guess)
Level 11
I found redis is functional on my vapor instance BUT some commands that work locally don't work on vapor (Win vs Linux?). ALSO, predis and phpredis do not behave the same, THEN using the Facades that handle the connection automatically hide the auto-complete I'd have using the classes directly... sigh.
Level 11
A hint on debugging environment issues on Vapor: in AWS Lambda is a page where you can see all the injected environment variables. There I saw that Vapor indeed uses phpredis, I saw the url/port/password to the redis instance, etc.
Level 5
@flap152, but you know the env names or the values? Thanks for this update, is very helpful
Level 3
Something that caught me out was needing to wrap the key in {} as it's in a cluster, eg Redis::smove('{myset.original}', '{myset.new}', $value);
Level 3
Doh! I'm gravedigging here!
Level 7
@flap152 did you by any chance find a solution to this? We are having the same problem
Level 11
@ITProperty Please understand it's 2 years later... No actual "solution" but we realized Vapor-AWS-redis used clusters that behave differently and don't necessarily support same instruction set. Pooling of commands was part of what we tried at the time, IIRC.
Please or to participate in this conversation.