sameersbn / sameersbn/docker-gitlab
REDIS Replacement
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I've spent several days building a complete new redis image.
I would to request an evaluation from the community, to see if we can use this as the basic redis image instead of sameersbn/docker-redis.
Source repository:
Both source repositories are the same.
Overview:
- alpine:3.4
- S6-Overlay
- redis:3.2.5
- master / slave support
- full sentinel support (optional, can be activated from docker-compose)
- full docker support for master / slave / sentinel
- USERMAP_UID/GID support which was requested with an issue on your repo.
- ability to run either redis-server or redis-sentinel or both within the same image.
For more information about sentinel: https://redis.io/topics/sentinel
I've thoroughly tested the master with multiple slaves with sentinel, automatic failover etc..., everything is working.
Also everything is documented within the README and I've provided 7 docker-compose examples, see the readme for more information.
I really hope everyone likes this new image, and are willing to evaluate it and look at the possibility to either reference it within docker-gitlab or fork my github repo.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the proposed docker-alpine-redis repositories, their README, and the seven docker-compose examples, then compare them with the current sameersbn/docker-redis image used by this project. Done means completing the community evaluation and deciding whether docker-gitlab should reference or fork the proposed image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, redis
- Domain
- databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100