gvsafronov/futriix
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

Rename systemd files and content to valkey from redis (#234)

Browse Source 
Changed systemd file names and content of them to valkey.

Signed-off-by: Shivshankar-Reddy <shiva.sheri.github@gmail.com>
This commit is contained in:
Shivshankar 2024-04-08 14:37:56 -04:00 committed by GitHub
parent 750e94cad3
commit 5bccd7b800
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 48 additions and 48 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
utils/systemd-redis_multiple_servers@.service
View File

@ -1,37 +0,0 @@
# example systemd template service unit file for multiple redis-servers
#
# You can use this file as a blueprint for your actual template service unit
# file, if you intend to run multiple independent redis-server instances in
# parallel using systemd's "template unit files" feature. If you do, you will
# want to choose a better basename for your service unit by renaming this file
# when copying it.
#
# Please take a look at the provided "systemd-redis_server.service" example
# service unit file, too, if you choose to use this approach at managing
# multiple redis-server instances via systemd.
[Unit]
Description=Redis data structure server - instance %i
Documentation=https://redis.io/documentation
# This template unit assumes your redis-server configuration file(s)
# to live at /etc/redis/redis_server_<INSTANCE_NAME>.conf
AssertPathExists=/etc/redis/redis_server_%i.conf
#Before=your_application.service another_example_application.service
#AssertPathExists=/var/lib/redis
[Service]
ExecStart=/usr/local/bin/redis-server /etc/redis/redis_server_%i.conf
LimitNOFILE=10032
NoNewPrivileges=yes
#OOMScoreAdjust=-900
#PrivateTmp=yes
Type=notify
TimeoutStartSec=infinity
TimeoutStopSec=infinity
UMask=0077
#User=redis
#Group=redis
#WorkingDirectory=/var/lib/redis
[Install]
WantedBy=multi-user.target

37
utils/systemd-valkey_multiple_servers@.service Normal file
View File

@ -0,0 +1,37 @@
# example systemd template service unit file for multiple valkey-servers
#
# You can use this file as a blueprint for your actual template service unit
# file, if you intend to run multiple independent valkey-server instances in
# parallel using systemd's "template unit files" feature. If you do, you will
# want to choose a better basename for your service unit by renaming this file
# when copying it.
#
# Please take a look at the provided "systemd-valkey_server.service" example
# service unit file, too, if you choose to use this approach at managing
# multiple valkey-server instances via systemd.
[Unit]
Description=Valkey data structure server - instance %i
Documentation=https://github.com/valkey-io/valkey-doc
# This template unit assumes your valkey-server configuration file(s)
# to live at /etc/valkey/valkey_server_<INSTANCE_NAME>.conf
AssertPathExists=/etc/valkey/valkey_server_%i.conf
#Before=your_application.service another_example_application.service
#AssertPathExists=/var/lib/valkey
[Service]
ExecStart=/usr/local/bin/valkey-server /etc/valkey/valkey_server_%i.conf
LimitNOFILE=10032
NoNewPrivileges=yes
#OOMScoreAdjust=-900
#PrivateTmp=yes
Type=notify
TimeoutStartSec=infinity
TimeoutStopSec=infinity
UMask=0077
#User=valkey
#Group=valkey
#WorkingDirectory=/var/lib/valkey
[Install]
WantedBy=multi-user.target

22
utils/systemd-redis_server.service → utils/systemd-valkey_server.service
View File

@ -1,13 +1,13 @@
# example systemd service unit file for redis-server
# example systemd service unit file for valkey-server
#
# In order to use this as a template for providing a redis service in your
# environment, _at the very least_ make sure to adapt the redis configuration
# In order to use this as a template for providing a valkey service in your
# environment, _at the very least_ make sure to adapt the valkey configuration
# file you intend to use as needed (make sure to set "supervised systemd"), and
# to set sane TimeoutStartSec and TimeoutStopSec property values in the unit's
# "[Service]" section to fit your needs.
#
# Some properties, such as User= and Group=, are highly desirable for virtually
# all deployments of redis, but cannot be provided in a manner that fits all
# all deployments of valkey, but cannot be provided in a manner that fits all
# expectable environments. Some of these properties have been commented out in
# this example service unit file, but you are highly encouraged to set them to
# fit your needs.
@ -16,16 +16,16 @@
# more information.
[Unit]
Description=Redis data structure server
Documentation=https://redis.io/documentation
Description=Valkey data structure server
Documentation=https://github.com/valkey-io/valkey-doc
#Before=your_application.service another_example_application.service
#AssertPathExists=/var/lib/redis
#AssertPathExists=/var/lib/valkey
Wants=network-online.target
After=network-online.target
[Service]
ExecStart=/usr/local/bin/valkey-server --supervised systemd --daemonize no
## Alternatively, have redis-server load a configuration file:
## Alternatively, have valkey-server load a configuration file:
#ExecStart=/usr/local/bin/valkey-server /path/to/your/valkey.conf
LimitNOFILE=10032
NoNewPrivileges=yes
@ -35,9 +35,9 @@ Type=notify
TimeoutStartSec=infinity
TimeoutStopSec=infinity
UMask=0077
#User=redis
#Group=redis
#WorkingDirectory=/var/lib/redis
#User=valkey
#Group=valkey
#WorkingDirectory=/var/lib/valkey
[Install]
WantedBy=multi-user.target