• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Redis with docker: How to provide file path for redis.conf as first argument?

Spring

New Pleskian
Server operating system version
Ubuntu 22.04.3 LTS
Plesk version and microupdate number
18.0.57
I installed Redis as docker-container (in Plesk Obsidian).

The Redis-doc says the following, when further configuration is needed:
# Redis configuration file example.
#
# Note that in order to read the configuration file, Redis must be
# started with the file path as first argument:
#
# ./redis-server /path/to/redis.conf

How can I provide the file path for this redis.conf as "first argument while starting Redis"?
 
With Docker Compose it works.

Recommended is then to use the INCLUDE-function
include /path/to/local.conf
of the redis.conf-file (Redis configuration file example) to provide through this way your editable configuration-file (local.conf). (Redis always uses the last processed line as value of a configuration directive.)

After updating the local.conf, restarting the docker-container (via Plesk-interface) is needed, so the new configuration can be loaded.

A big thank you goes to the webhoster [redacted, URL of webhoster; we avoid such links, because they can create an unfair market advantage for some web hosters on this forum] for their perseverance in trying this out!
 
Last edited by a moderator:
Back
Top