-
Notifications
You must be signed in to change notification settings - Fork 72
Blog post: How to Properly Secure Your Valkey Deployment #389
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
base: main
Are you sure you want to change the base?
Conversation
|
Bump @madolson or @stockholmux for review |
|
On it now! Sorry for the delay, some work fires recently :) |
madolson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the structure, some nits and misc recommendations, but I think it's close.
content/blog/2025-10-15-properly-secure-your-valkey-deployment.md
Outdated
Show resolved
Hide resolved
content/blog/2025-10-15-properly-secure-your-valkey-deployment.md
Outdated
Show resolved
Hide resolved
content/blog/2025-10-15-properly-secure-your-valkey-deployment.md
Outdated
Show resolved
Hide resolved
content/blog/2025-10-15-properly-secure-your-valkey-deployment.md
Outdated
Show resolved
Hide resolved
content/blog/2025-10-15-properly-secure-your-valkey-deployment.md
Outdated
Show resolved
Hide resolved
content/blog/2025-10-15-properly-secure-your-valkey-deployment.md
Outdated
Show resolved
Hide resolved
|
Thank you for the thorough review, @madolson! I just pushed a change that incorporates all your feedback 👍 |
Description
Blog post: How to Properly Secure Your Valkey Deployment
Issues Resolved
#388
Check List
--signoffBy submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.