I just upgraded v.2.0 beta but don’t see any option to enable Redis.
Is Redis enabled by default somewhere or do we have to do something else?
What about HTTP/2? Will it be automatically enabled if using HTTPS?
Hi Jon,
HTTP/2 is enabled by default. You must access the site with HTTPS. If it’s not HTTP/2 try restarting the site.
As far as Redis goes, the site must be created after upgrading to 2.0. One easy way to upgrade the site container is to export the site then re-import it.
Where would Redis info show up on the Mac 2.0 app?
I followed your instructions but still do not see it… or is it automatically enabled in background?
Redis starts automatically for any site using the “Custom” environment that was created after upgrading to Local 2.0.
If you install this plugin and activate it, it should just work.
@clay is it possible to access Redis outside from container? Similar way we have access to MySQL DBs.
There aren’t any ports exposed for Redis at the moment.
Are you wanting this to manage Redis from outside of the site container or are there other reasons?
It’s always nice to have option for GUI like Medis to check data. I can use WP-CLI, before ports are exposed for Redis.
1 Like
@clay After install plugin i am seeing this screen Can you guide me what else I have to cofigure
Hey Ravinder,
You should be good as long as you have Object Cache enabled on that plugin like you do in that screenshot.
Is it still saying “Not Connected”?
@clay This screenshot is from new instance. it is showing predis instead of pecl but still not connected . Can you tell which one is correct and how this can I configure it
It looks like that site might be using the Preferred environment. If so, Redis is only available in the Custom environment.
You can easily change to Custom by right-clicking on the site, Exporting, then re-importing using the Custom environment.
We’re working on docs to clear up this confusion.
@clay thank you for help. Connected now.
1 Like
Howdy.
There aren’t any ports exposed for Redis at the moment.
Are you wanting this to manage Redis from outside of the site container or are there other reasons?
So, one big issue that we are seeing is that when we run wpcli from the host machine (e.g. GitHub - bigwing/local-wp-cli: Run WP CLI commands from your terminal without having to SSH into Local by Flywheel machine. and https://github.com/jtsternberg/Dot-Files/blob/master/bin/local-wpcli-config), the WPCLI instance does not use the same Redis cache (or use a cache at all). This is problematic for some obvious reasons, like DB operations that do not update the Local VM’s cache.
So yes, it would be great to expose the ports so that we can define the redis connection from the host machine for wpcli operations.