Skip to content

Add Valkey support to Winter CMS documentation #244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

rlunar
Copy link

@rlunar rlunar commented Jul 30, 2025

Summary

  • Add comprehensive documentation for Valkey as a cache and session driver
  • Include installation, configuration, and usage examples
  • Update existing cache documentation to include Valkey alongside Redis options
  • Document Valkey as a Redis-compatible alternative for caching, queues, and sessions

Files to Modify/Add

New Documentation Files:

  • services/cache.md - Update cache service documentation to include Valkey configuration options
  • services/queues.md - Update queues service documentation with Valkey support details
  • services/session.md - Update session service documentation with Valkey configuration
  • setup/configuration.md - Add Valkey environment variables

- Update cache service documentation to include Valkey configuration options
- Update queues service documentation with Valkey support details
- Update session service documentation with Valkey configuration
- Document Valkey as a Redis-compatible alternative for caching, queues, and sessions
Copy link
Member

@bennothommo bennothommo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rlunar thanks for your submission. While we'd be happy to mention Valkey in our docs, we don't want to advocate for Valkey over Redis (or vice-versa). Could you please make the following changes.

Comment on lines +117 to +124
### Valkey

[Valkey](https://valkey.io) is an open-source, high-performance key-value datastore that serves as a drop-in replacement for Redis. It offers the same functionality and performance as Redis while being community-driven with improved governance.

Since Valkey is protocol-compatible with Redis, it uses the same configuration as Redis. You can use the existing Redis configuration section in `config/database.php` for Valkey connections. Both the `predis` and `phpredis` clients work seamlessly with Valkey, requiring no additional configuration changes.

To use Valkey instead of Redis, simply point your Redis configuration to your Valkey server instance. All Redis configuration examples in this documentation apply equally to Valkey.

Copy link
Member

@bennothommo bennothommo Jul 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section reads too much like a promotion of Valkey. I'd prefer if we do not include a section for Valkey and just change the Redis section above to "Redis / Valkey" instead as necessary, with maybe a small mention that Valkey is a drop-in replacement for Redis.

Suggested change
### Valkey
[Valkey](https://valkey.io) is an open-source, high-performance key-value datastore that serves as a drop-in replacement for Redis. It offers the same functionality and performance as Redis while being community-driven with improved governance.
Since Valkey is protocol-compatible with Redis, it uses the same configuration as Redis. You can use the existing Redis configuration section in `config/database.php` for Valkey connections. Both the `predis` and `phpredis` clients work seamlessly with Valkey, requiring no additional configuration changes.
To use Valkey instead of Redis, simply point your Redis configuration to your Valkey server instance. All Redis configuration examples in this documentation apply equally to Valkey.

@@ -11,7 +11,7 @@ The session configuration is stored in `config/session.php`. Be sure to review t
- `file` - sessions are stored in `storage/framework/sessions`.
- `cookie` - sessions are stored in secure, encrypted cookies.
- `database` - sessions are stored in a database used by your application.
- `memcached` / `redis` - sessions are stored in one of these fast, cache based stores.
- `memcached` / `redis` / `valkey` - sessions are stored in one of these fast, cache based stores.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

valkey is not an applicable session driver as far as I know. Valkey still uses the redis driver.

Suggested change
- `memcached` / `redis` / `valkey` - sessions are stored in one of these fast, cache based stores.
- `memcached` / `redis` - sessions are stored in one of these fast, cache based stores.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants