A missing blog post image

Introduction

I’ve just achieved one more Redis installation today, and as the previous ones, I had to browse the WEB again, looking for the same pieces of information.
You’ll find below my Redis-installation-memo (at least for me, in the future).

No slow listening TCP sockets. Only a hardened UNIX one.
No boot warnings. Only Linux kernel tweaks.
Not so many databases. Only what we usually need.
No hand-made BASH scripts for standalone program administration. Only a systemd-supervised instance.

A procedure powered by Debian :heart:

The procedure

aptitude install -y redis-server

systemctl stop redis-server.service

nano /etc/redis/redis.conf
: '
# ...
port 0
# ...
tcp-backlog 128
# ...
unixsocket /var/run/redis/redis.sock
unixsocketperm 770
# ...
supervised systemd
# ...
databases 1
# ...
requirepass <at-least-a-64-byte-long-random-string>
'

sysctl -w vm.overcommit_memory=1
echo -e '\n\n# REDIS\nvm.overcommit_memory = 1' >> /etc/sysctl.d/local.conf

systemctl edit --full redis-server.service
: '
# ...

[Service]
Type=notify
# ...
ExecStartPre=/bin/echo "never" > /sys/kernel/mm/transparent_hugepage/enabled

# ...
'

systemctl daemon-reload
systemctl start redis-server.service

At this time the server should be up and running, you may want to check that everything went fine this way :

tail /var/log/redis/redis-server.log

For Redis usage from PHP-based applications you’ll need :

usermod -a -G redis www-data

# Using `mod_php` ?
systemctl restart apache2

# Using FPM ? 
systemctl restart php7.X-fpm

Conclusion

No conclusion. It should work, even for you, young WEB-wanderer.