Valkey support

Open Beginner friendly
#81 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker, python, redis
Domain
databases

Research direction

No file or test is named. Start by locating the existing Redis provider patterns and the Docker database-provider handling; add Valkey support alongside the Redis-compatible providers. Done means a Valkey database container is recognized and backed up, with the relevant tests passing if the project has coverage for provider detection.

Written by the indexing model from the issue text.

Description

Sine redis became proprietary about a year ago, many projects are switching to valkey (https://hub.docker.com/r/valkey/valkey/)

It's a drop-in replacement, so it should just be a matter of adding it to the provider patterns for redis.

Dominant language
Python
Stars
201
Forks
27
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from RealOrangeOne/docker-db-auto-backup

All issues in RealOrangeOne/docker-db-auto-backup

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.