Builds Redis and every module upstream bundles with it from a single source, and ships two things you can install:
| Package | What you get |
|---|---|
redis-core |
Plain server: redis-server, redis-cli, redis-sentinel. Vector sets included (compiled into the binary). No modules. |
redis |
The same server plus RediSearch, RedisJSON, RedisBloom and RedisTimeSeries, active on restart. |
sudo dnf copr enable @redis/redis
sudo dnf install redis-core # plain
# or
sudo dnf install redis # everything
sudo systemctl enable --now redisThere is no partial state: either no modules, or all of them.
redis-devel is also built, for compiling third-party modules against this Redis.
Redis 8.x pins each bundled module to an exact upstream ref in
modules/modules.yaml and builds them through its own modules/common.mk +
scripts/build.sh. Packaging that as one SRPM means module versions can
never drift from the core they were tested against, and there is a single
place to bump.
This replaces five previously separate packaging repos. See docs/DESIGN.md for how that decision was reached and what it costs.
make help # list every target
make check-tools # verify your toolchain
make sources # regenerate the generated tarballs (needs network)
make srpm # build the source RPM
make mock # build locally in a clean chroot (~1h on 2 cores)
make smoke # install from Copr and test every moduleFull pipeline: make all (sources → srpm → mock → lint).
redis.spec the only file you edit for a version bump
Makefile reproducible build + test entry points
sources/ static sources: systemd units, sysusers,
logrotate, the redis.conf patch, rpmlintrc
scripts/
make-sources.sh regenerates the two vendored crate tarballs
smoke-test.sh installs into a throwaway root and asserts behaviour
docs/
DESIGN.md why one SRPM with subpackages; what was rejected
BUILDING.md how the build works, and every offline-build trap
TESTING.md what the smoke tests prove, and how to run them
MAINTENANCE.md step-by-step version bump procedure
- docs/DESIGN.md — the packaging model and the reasoning
- docs/BUILDING.md — build mechanics and offline gotchas
- docs/TESTING.md — how the packages are verified
- docs/MAINTENANCE.md — bumping to a new Redis release
- AGENTS.md — guidance for coding agents working on this repo (also the place the non-obvious failure modes are written down)
- MAINTAINERS.md — provenance, ownership, open decisions