curl https://exampleconfig.com/api/v1/config/original/1b0b436832a3318b8996c52a80889009?hint=redis-server@.service
wget -O redis-server@.service https://exampleconfig.com/api/v1/config/original/1b0b436832a3318b8996c52a80889009?hint=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
sudo apk add redis
sudo apt update && sudo apt install redis-server
sudo apt update && sudo apt install redis-server
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.
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.
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.
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.
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.