Redis Insight configuration settings
Environment variables
Variable | Purpose | Default | Additional info |
---|---|---|---|
RI_APP_PORT | The port that Redis Insight listens on |
|
See Express Documentation |
RI_APP_HOST | The host that Redis Insight connects to |
|
See Express Documentation |
RI_SERVER_TLS_KEY | Private key for HTTPS | n/a | Private key in PEM format. Can be a path to a file or a string in PEM format. |
RI_SERVER_TLS_CERT | Certificate for supplied private key | n/a | Public certificate in PEM format. Can be a path to a file or a string in PEM format. |
RI_ENCRYPTION_KEY | Key to encrypt data with | n/a | Available only for Docker. Redis insight stores sensitive information (database passwords, Workbench history, etc.) locally (using sqlite3). This variable allows you to store sensitive information encrypted using the specified encryption key. Note: The same encryption key should be provided for subsequent docker run commands with the same volume attached to decrypt the information. |
RI_LOG_LEVEL | Configures the log level of the application. | info |
Supported logging levels are prioritized from highest to lowest:
|
RI_FILES_LOGGER | Logs to file | true |
By default, you can find log files in the following folders:
|
RI_STDOUT_LOGGER | Logs to STDOUT | true |
|
RI_PROXY_PATH | Configures a subpath for a proxy | n/a | Available only for Docker. |
Use Redis Insight behind a reverse proxy
When you configure Redis Insight to run behind a reverse proxy like NGINX, set the request timeout to over 30 seconds on the reverse proxy because some requests can be long-running.
Redis Insight also allows you to manage its connection timeout on the form to configure the connection details. The default timeout is 30 seconds.
Hosting Redis Insight behind a prefix path (path-rewriting) is not supported.