Update futriix.conf

futriix.conf

@@ -1,9 +1,9 @@
-# Valkey configuration file example.
+# Futriix configuration file example.
 #
 # Note that in order to read the configuration file, the server must be
 # started with the file path as first argument:
 #
-# ./valkey-server /path/to/valkey.conf
+# ./futriix-server /path/to/futriix.conf
 
 # Note on units: when memory size is needed, it is possible to specify
 # it in the usual form of 1k 5GB 4M and so forth:
@@ -49,7 +49,7 @@
 # Load modules at startup. If the server is not able to load modules
 # it will abort. It is possible to use multiple loadmodule directives.
 #
-# loadmodule /path/to/my_module.so
+loadmodule /home/grigoriy/futriix/futriixjson.so
 # loadmodule /path/to/other_module.so
 # loadmodule /path/to/args_module.so [arg [arg ...]]
 
@@ -197,8 +197,8 @@ tcp-keepalive 300
 # server to connected clients, primaries or cluster peers.  These files should be
 # PEM formatted.
 #
-# tls-cert-file valkey.crt
-# tls-key-file valkey.key
+# tls-cert-file futriix.crt
+# tls-key-file futriix.key
 #
 # If the key file is encrypted using a passphrase, it can be included here
 # as well.
@@ -226,7 +226,7 @@ tcp-keepalive 300
 # required by older versions of OpenSSL (<3.0). Newer versions do not require
 # this configuration and recommend against it.
 #
-# tls-dh-params-file valkey.dh
+# tls-dh-params-file futriix.dh
 
 # Configure a CA certificate(s) bundle or directory to authenticate TLS/SSL
 # clients and peers. The server requires an explicit configuration of at least one
@@ -385,7 +385,7 @@ daemonize no
 #
 # Note that on modern Linux systems "/run/valkey.pid" is more conforming
 # and should be used instead.
-pidfile /var/run/valkey_6379.pid
+pidfile /var/run/futriix_9880.pid
 
 # Specify the server verbosity level.
 # This can be one of: