Skip to content

Commit 4ade92f

Browse files
committed
ref: bring back single node docs
1 parent d6b29d3 commit 4ade92f

File tree

1 file changed

+28
-0
lines changed

1 file changed

+28
-0
lines changed
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
title: Simple Single Node
3+
sidebar_title: Simple Single Node
4+
sidebar_order: 1
5+
---
6+
7+
This is the simplest setup for self-hosted Sentry. It is recommended for small to medium-sized installations. This setup follows [the minimum requirements](/self-hosted/#required-minimum-system-resources) for running Sentry.
8+
9+
It is highly recommended to put an external load balancer (or reverse proxy) in front of your self-hosted Sentry deployment. That way, you can tweak on rate limiting, TLS termination, and other features that does not change the built-in nginx configuration file. It is recommended to install the load balancer on your host machine instead of as a Docker container. Doing this way helps you in the event of Docker engine failure.
10+
11+
If using external load balancer is not possible, you can put it as a Docker container, pointing to the `nginx` service at port `80`. Whatever value you put on your `SENTRY_BIND` environment variable won't matter.
12+
13+
```mermaid
14+
graph TB
15+
subgraph Server
16+
direction TB
17+
nginx[External Nginx]
18+
sentry[Self-Hosted Sentry]
19+
20+
nginx --> sentry
21+
end
22+
23+
internet[Public Internet]
24+
25+
internet--> Server
26+
```
27+
28+
For more information regarding configuring your external load balancer, please refer to the [External Load Balancer](/self-hosted/experimental/reverse-proxy/) section.

0 commit comments

Comments
 (0)