Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DEV: re-do RI changes #192

Merged
merged 1 commit into from
May 8, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 2 additions & 9 deletions content/develop/connect/insight/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,8 @@ Redis Insight includes an opt-in telemetry system. This help us improve the deve

## Log files

To get detailed information about errors in Redis Insight, you can review the log files with the `.log` extension in the appropriate location:
You can review the Redis Insight log files (files with a `.log` extension) to get detailed information about system issues.
These are the locations on supported platforms:

- **Docker**: In the `/data/logs` directory *inside the container*.
- **Mac**: In the `/Users/<your-username>/.redis-insight` directory.
Expand All @@ -132,14 +133,6 @@ To get detailed information about errors in Redis Insight, you can review the lo
You can install Redis Insight on operating systems that are not officially supported, but it may not behave as expected.
{{< /note >}}

## Using behind a reverse proxy

When you configure Redis Insight to run behind a reverse proxy like [NGINX](https://www.nginx.com/):

- Because some requests can be long-running, it is recommended that the request timeout is set to over 30 seconds on the reverse proxy.
Redis Insight also allows you to manage its connection timeout, which is 30 seconds by default, on the form to manage the connection details.
- Hosting Redis Insight behind a prefix path (path-rewriting) is not supported.

## Feedback

To provide your feedback, [open a ticket in our Redis Insight repository](https://github.com/Redis-Insight/Redis-Insight/issues/new).
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -3,14 +3,11 @@ categories:
- docs
- operate
- redisinsight
description: 'Redis Insight supported environment variables

'
linkTitle: Environment variables
title: Environment variables
linkTitle: Configuration settings
title: Redis Insight configuration settings
weight: 5
---
You can configure Redis Insight with the following environment variables.
## Environment variables

| Variable | Purpose | Default | Additional info |
| --- | --- | --- | --- |
Expand All @@ -23,3 +20,11 @@ You can configure Redis Insight with the following environment variables.
| RI_FILES_LOGGER | Logs to file | `true` | By default, you can find log files in the following folders: <ul> <li> Docker: `/data/logs` <li> desktop: `<user-home-dir>/.redisinsight-app/logs` </ul>|
| 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](https://www.nginx.com/), 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.
160 changes: 0 additions & 160 deletions content/operate/redisinsight/install/configuration.md

This file was deleted.