mirror of
https://github.com/fosrl/docs-v2.git
synced 2026-02-21 04:16:43 +00:00
reorg
This commit is contained in:
@@ -60,7 +60,7 @@ Path match rules allow URL patterns defined with plain text and wildcards (`*`)
|
||||
### Country
|
||||
|
||||
<Note>
|
||||
Geo blocking is only available for targets created with managed nodes or in the cloud because we need to host services to resolve IP addresses and evolve it quickly as network change.
|
||||
Geo blocking is only available for targets created with managed self-hosted nodes or in the cloud because we need to host services to resolve IP addresses and evolve it quickly as network change.
|
||||
|
||||
Fully self hosted users can install a [Traefik plugin](/self-host/community-guides/geoblock) for geo blocking support.
|
||||
</Note>
|
||||
|
||||
@@ -3,10 +3,6 @@ title: "Add Client"
|
||||
description: "Create a client to connect to your Pangolin network from a remote computer"
|
||||
---
|
||||
|
||||
<Note>
|
||||
This feature is only available in self-hosted Pangolin instances.
|
||||
</Note>
|
||||
|
||||
A client in Pangolin is a way to create a traditional VPN tunnel from your remote computer to your Newt site on your private network. Clients allow you to tunnel your computer back into your whole network and remotely access non-HTTP resources like file shares or use it as a bastion host to manage servers.
|
||||
|
||||
<Note>
|
||||
|
||||
@@ -69,7 +69,7 @@ Domains can be added to an organization via the domains section of the organizat
|
||||
</Steps>
|
||||
|
||||
<Warning>
|
||||
Domain delegation and CNAME domains are only available in Pangolin Cloud. Self-hosted Pangolin uses different domain configuration methods.
|
||||
Domain delegation and CNAME domains are only available in Pangolin Cloud. Community Edition Pangolin uses different domain configuration methods.
|
||||
</Warning>
|
||||
|
||||
### Self-Hosted Pangolin
|
||||
|
||||
@@ -4,7 +4,7 @@ description: "Configure automated health monitoring and failover for high availa
|
||||
---
|
||||
|
||||
<Note>
|
||||
Health checks are only available for targets created with managed nodes or in the cloud.
|
||||
Health checks are only available for targets created with managed self-hosted nodes or in the cloud.
|
||||
</Note>
|
||||
|
||||
<iframe
|
||||
@@ -222,4 +222,4 @@ Resource: api-service
|
||||
└── api-02.backup:8443 - Healthy ✅
|
||||
|
||||
All targets receive traffic via load balancing
|
||||
```
|
||||
```
|
||||
|
||||
@@ -4,7 +4,7 @@ description: "Configure external identity providers for user authentication"
|
||||
---
|
||||
|
||||
<Note>
|
||||
Identity providers are only available in self-hosted Pangolin instances.
|
||||
Identity providers are only available in Community Edition Pangolin instances.
|
||||
</Note>
|
||||
|
||||
Identity providers let you authenticate Pangolin users using external identity providers. This is useful for organizations that want to use their existing identity provider infrastructure to manage user authentication.
|
||||
|
||||
@@ -45,7 +45,7 @@ Organization API keys are created by organization admins and have limited scope
|
||||
|
||||
### Root API Keys
|
||||
|
||||
Root API keys have some extra permissions and can execute operations across orgs. They are only available in self-hosted Pangolin:
|
||||
Root API keys have some extra permissions and can execute operations across orgs. They are only available in the Community Edition of Pangolin:
|
||||
|
||||
<Warning>
|
||||
Root API keys have elevated permissions and should be used carefully. Only create them when you need server-wide access.
|
||||
|
||||
@@ -45,7 +45,7 @@ Organization API keys are created by organization admins and have limited scope
|
||||
|
||||
### Root API Keys
|
||||
|
||||
Root API keys have some extra permissions and can execute operations across orgs. They are only available in self-hosted Pangolin:
|
||||
Root API keys have some extra permissions and can execute operations across orgs. They are only available in the Community Edition Pangolin:
|
||||
|
||||
<Warning>
|
||||
Root API keys have elevated permissions and should be used carefully. Only create them when you need server-wide access.
|
||||
|
||||
@@ -37,22 +37,22 @@ The managed self-hosted approach gives you the best of both worlds:
|
||||
|
||||
## Key Benefits
|
||||
|
||||
### ✅ Simpler Operations
|
||||
### Simpler Operations
|
||||
No need to run your own mail server or set up complex alerting. You'll get health checks and downtime alerts out of the box, making it much easier to monitor your infrastructure without additional complexity.
|
||||
|
||||
### 🔄 Automatic Updates
|
||||
### Automatic Updates
|
||||
The cloud dashboard evolves quickly, so you get new features and bug fixes without having to manually pull new containers every time. Your self-hosted node stays current automatically.
|
||||
|
||||
### 🔧 Less Maintenance
|
||||
### Less Maintenance
|
||||
No database migrations, backups, or extra infrastructure to manage. We handle that in the cloud, so you can focus on what matters most to your business.
|
||||
|
||||
### 📊 Cloud Failover
|
||||
### Cloud Failover
|
||||
If your node goes down, your tunnels can temporarily fail over to our cloud points of presence until you bring it back online. This ensures continuous availability even during maintenance windows.
|
||||
|
||||
### 🛡️ High Availability (PoPs)
|
||||
### High Availability (PoPs)
|
||||
You can also attach multiple nodes to your account for redundancy and better performance. Deploy nodes across different regions or providers for maximum reliability.
|
||||
|
||||
### ⚡ Future Enhancements
|
||||
### Future Enhancements
|
||||
We're planning to add more analytics, alerting, and management tools to make your deployment even more robust. You'll automatically benefit from these improvements as they're released.
|
||||
|
||||
## Getting Started
|
||||
@@ -69,4 +69,4 @@ Ready to convert your existing self-hosted node to managed? Learn how in our [co
|
||||
|
||||
<Tip>
|
||||
Managed deployment is ideal for organizations that need high availability and reduced operational overhead while maintaining complete control over their infrastructure and data transit.
|
||||
</Tip>
|
||||
</Tip>
|
||||
|
||||
Reference in New Issue
Block a user