Redis /etc/systemd/redis-server@.service
Authentic
📋 Debian 10 (Buster)
74 lines
Compatibility
Currently viewing:
Debian 10 (Buster)
Also compatible:
Different versions:
File Info
- Size
- 74 lines
- MD5
- 1b0b436832a3318b8996c52a80889009
- SHA256
- b65ac9e97f7021911506daffe20101d0e00c1dca995b182e7ee338827eb764d1
Quick Commands
curl:
curl https://exampleconfig.com/api/v1/config/original/1b0b436832a3318b8996c52a80889009?hint=redis-server@.service
wget:
wget -O redis-server@.service https://exampleconfig.com/api/v1/config/original/1b0b436832a3318b8996c52a80889009?hint=redis-server@.service
/etc/systemd/redis-server@.service
# Templated service file for redis-server(1)
#
# Each instance of redis-server requires its own configuration file:
#
# $ cp /etc/redis/redis.conf /etc/redis/redis-myname.conf
# $ chown redis:redis /etc/redis/redis-myname.conf
#
# Ensure each instance is using their own database:
#
# $ sed -i -e 's@^dbfilename .*@dbfilename dump-myname.rdb@' /etc/redis/redis-myname.conf
#
# We then listen exlusively on UNIX sockets to avoid TCP port collisions:
#
# $ sed -i -e 's@^port .*@port 0@' /etc/redis/redis-myname.conf
# $ sed -i -e 's@^\(# \)\{0,1\}unixsocket .*@unixsocket /var/run/redis-myname/redis-server.sock@' /etc/redis/redis-myname.conf
#
# ... and ensure we are logging, etc. in a unique location:
#
# $ sed -i -e 's@^logfile .*@logfile /var/log/redis/redis-server-myname.log@' /etc/redis/redis-myname.conf
# $ sed -i -e 's@^pidfile .*@pidfile /run/redis-myname/redis-server.pid@' /etc/redis/redis-myname.conf
#
# We can then start the service as follows, validating we are using our own
# configuration:
#
# $ systemctl start redis-server@myname.service
# $ redis-cli -s /var/run/redis-myname/redis-server.sock info | grep config_file
#
# -- Chris Lamb <lamby@debian.org> Mon, 09 Oct 2017 22:17:24 +0100
[Unit]
Description=Advanced key-value store (%I)
After=network.target
Documentation=http://redis.io/documentation, man:redis-server(1)
[Service]
Type=forking
ExecStart=/usr/bin/redis-server /etc/redis/redis-%i.conf
ExecStop=/bin/kill -s TERM $MAINPID
PIDFile=/run/redis-%i/redis-server.pid
TimeoutStopSec=0
Restart=always
User=redis
Group=redis
RuntimeDirectory=redis-%i
RuntimeDirectoryMode=2755
UMask=007
PrivateTmp=yes
LimitNOFILE=65535
PrivateDevices=yes
ProtectHome=yes
ReadOnlyDirectories=/
ReadWriteDirectories=-/var/lib/redis
ReadWriteDirectories=-/var/log/redis
ReadWriteDirectories=-/var/run/redis-%i
NoNewPrivileges=true
CapabilityBoundingSet=CAP_SETGID CAP_SETUID CAP_SYS_RESOURCE
MemoryDenyWriteExecute=true
ProtectKernelModules=true
ProtectKernelTunables=true
ProtectControlGroups=true
RestrictRealtime=true
RestrictNamespaces=true
RestrictAddressFamilies=AF_INET AF_INET6 AF_UNIX
# redis-server can write to its own config file when in cluster mode so we
# permit writing there by default. If you are not using this feature, it is
# recommended that you replace the following lines with "ProtectSystem=full".
ProtectSystem=true
ReadWriteDirectories=-/etc/redis
[Install]
WantedBy=multi-user.target
How to Install Redis
Alpine Linux
sudo apk add redis
Debian
sudo apt update && sudo apt install redis-server
Ubuntu
sudo apt update && sudo apt install redis-server
Configuration File Location
Complete Redis Configuration Guide
- What is redis-server@.service?
- Access the original 'redis-server@.service' (redis.conf) configuration file from a fresh Redis installation on Debian 10 (Buster). This is the factory-default configuration for the world's most popular in-memory database, perfect for caching optimization, session management, and real-time application development.
- Technical Details
- Located at '/etc/systemd/redis-server@.service', this 74-line file controls memory policies, persistence options, clustering settings, pub/sub configurations, and security parameters. Powers caching for Twitter, GitHub, Instagram, and millions of high-performance applications requiring sub-millisecond response times.
- Common Configuration Question
- How do you configure Redis for optimal caching, session storage, and real-time features on Debian 10?
- Why Use This Configuration?
- This default configuration includes memory optimization, persistence strategies, and clustering support. Essential for backend developers, DevOps engineers, and architects building scalable applications with caching, queues, and real-time features.
Frequently Asked Questions
When should I use this redis-server@.service file?
Use this original configuration file when you need to restore Redis to its default state after misconfiguration, during fresh installations, or as a baseline for customization. It's particularly useful for troubleshooting when your current config isn't working properly.
How do I restore Redis to default settings?
Download this file and replace your current configuration at /etc/systemd/redis-server@.service. Make sure to backup your existing configuration first, then restart the Redis service to apply the changes.
Is this redis-server@.service file secure for production use?
This is the factory-default configuration that ships with Redis on Debian 10 (Buster). While it provides a secure baseline, you should review and customize security settings based on your specific production requirements and compliance needs.
What's the difference between this and other OS versions?
This configuration is specifically from Debian 10 (Buster). Different operating systems and versions may have slightly different default settings, security patches, or feature availability. Check the compatibility section above for other OS versions.
Can I use this configuration file for Redis troubleshooting?
Yes, this original configuration is excellent for troubleshooting. Compare it with your current settings to identify modifications that might be causing issues, or temporarily replace your config with this one to isolate problems.
