Self-Hosting in Digital Ocean, Upgrading Managed Caching from Redis to Valkey

Help
1

Hi all!

I have a self-hosted production instance of Directus 11 that has been running in Digital Ocean for the last 6 months. This uses uses Digital Ocean managed database (postgres), caching, spaces, etc. With Digital Ocean moving from Redis to Valkey for caching I wanted to see if others who are also hosting on Digital Ocean who have moved forward with the required “upgrade” to Valkey.

From what I can tell, they should be API compatible but wanted to be prepared for any configuration changes or compatibility issues before the upgrade is forced at the end of the month.

Thanks for any insights!

1 Answer

1
2

I’ve still got a few boxes for older personal projects over there - but I’m running Redis within the droplets using Docker.

As long as it’s compatible with Redis, I don’t see why there would be any issues. But I’ve not tested Valkey personally.

Also curious to see how it plays out since Redis is open source again now.

Thanks for the insights Bryant! To test, I provisioned a new instance of Directus within Digital Oceans App Platform and used the same environment variables/configuration that I have in my staging/production instances only using Valkey instead of Redis and everything seemed to work okay. Based on this, we are planning on upgrading both our staging and production caches over the weekend. Once complete, I will leave a follow up here for others who may be self-hosting in a similar way and who have concerns about the Digital Ocean forced upgrade. Thanks again!

 –