mirror of
https://github.com/fosrl/docs-v2.git
synced 2026-02-11 07:26:42 +00:00
enhance(enterprise): Consistent naming scheme and update quick install
Standardize edition-gated terminology to Enterprise Edition across docs where feature availability is described. Add links to /self-host/enterprise-edition so users can quickly understand edition differences before enabling gated features or selecting an installer edition.
This commit is contained in:
@@ -4,10 +4,10 @@ description: "Control your own Pangolin node with cloud management"
|
||||
---
|
||||
|
||||
<Note>
|
||||
Remote Nodes are available in Pangolin Enterprise and Pangolin Cloud.
|
||||
Remote Nodes are available in Pangolin Cloud and self-hosted [Enterprise Edition](/self-host/enterprise-edition).
|
||||
</Note>
|
||||
|
||||
Remote nodes, you run your own Pangolin node - your tunnels, SSL termination, and traffic all stay on your server and use your bandwidth. The difference is that management and monitoring are handled through our cloud or your central Pangolin Enterprise server. The node just handles terminating Wireguard tunnels, serving HTTP(S) traffic, and routing relayed client connections - it is essentially a remote networking hub.
|
||||
Remote nodes, you run your own Pangolin node - your tunnels, SSL termination, and traffic all stay on your server and use your bandwidth. The difference is that management and monitoring are handled through our cloud or your central self-hosted [Enterprise Edition](/self-host/enterprise-edition) server. The node just handles terminating Wireguard tunnels, serving HTTP(S) traffic, and routing relayed client connections - it is essentially a remote networking hub.
|
||||
|
||||
Think of different nodes as the "front doors" to your applications - users connect to the closest one, and it securely routes their requests to your backend services.
|
||||
|
||||
@@ -35,4 +35,4 @@ The cloud dashboard evolves quickly, so you get new features and bug fixes witho
|
||||
If your nodes goes down, your tunnels can temporarily fail over to our cloud points of presence or another node until you bring it back online. This ensures continuous availability.
|
||||
|
||||
### High Availability (PoPs)
|
||||
You can attach multiple nodes to your account for redundancy and better performance. For example, deploy nodes across different regions or providers for decreased latency.
|
||||
You can attach multiple nodes to your account for redundancy and better performance. For example, deploy nodes across different regions or providers for decreased latency.
|
||||
|
||||
Reference in New Issue
Block a user