mirror of
https://github.com/fosrl/docs-v2.git
synced 2026-02-08 05:56:45 +00:00
Fix broken links
This commit is contained in:
@@ -48,7 +48,7 @@ nodes provide a mesh of high availability - if one location goes down, traffic a
|
|||||||
Fully self-hosted, self-contained Pangolin server acting as a single node.
|
Fully self-hosted, self-contained Pangolin server acting as a single node.
|
||||||
</Card>
|
</Card>
|
||||||
|
|
||||||
<Card title="Learn More" icon="book" href="/manage/points-of-presence">
|
<Card title="Learn More" icon="book" href="/manage/nodes">
|
||||||
Detailed information about nodes and high availability options.
|
Detailed information about nodes and high availability options.
|
||||||
</Card>
|
</Card>
|
||||||
</CardGroup>
|
</CardGroup>
|
||||||
|
|||||||
@@ -64,7 +64,7 @@ Pangolin provides secure, application-specific ingress and routing without the l
|
|||||||
Edge networks don't need public IP addresses.
|
Edge networks don't need public IP addresses.
|
||||||
</Card>
|
</Card>
|
||||||
|
|
||||||
<Card title="Highly Available Mesh" icon="circle-nodes" href="/manage/points-of-presence">
|
<Card title="Highly Available Mesh" icon="circle-nodes" href="/manage/nodes">
|
||||||
Multiple nodes ensure high availability.
|
Multiple nodes ensure high availability.
|
||||||
</Card>
|
</Card>
|
||||||
</CardGroup>
|
</CardGroup>
|
||||||
|
|||||||
@@ -14,7 +14,7 @@ Pangolin establishes secure connections from edge networks to nodes, bypassing t
|
|||||||
<Card title="How it works" icon="map" href="/about/how-pangolin-works">
|
<Card title="How it works" icon="map" href="/about/how-pangolin-works">
|
||||||
Learn how the Pangolin system works from the server to the edge network.
|
Learn how the Pangolin system works from the server to the edge network.
|
||||||
</Card>
|
</Card>
|
||||||
<Card title="nodes" icon="circle-nodes" href="/manage/points-of-presence">
|
<Card title="nodes" icon="circle-nodes" href="/manage/nodes">
|
||||||
Learn about how Pangolin provides highly available ingress to your backend.
|
Learn about how Pangolin provides highly available ingress to your backend.
|
||||||
</Card>
|
</Card>
|
||||||
</Columns>
|
</Columns>
|
||||||
@@ -34,7 +34,7 @@ Pangolin establishes secure connections from edge networks to nodes, bypassing t
|
|||||||
<Card
|
<Card
|
||||||
title="Install Site"
|
title="Install Site"
|
||||||
icon="sitemap"
|
icon="sitemap"
|
||||||
href="/manage/sites/install-newt"
|
href="/manage/sites/install-site"
|
||||||
>
|
>
|
||||||
Install Newt, the edge client, almost anywhere.
|
Install Newt, the edge client, almost anywhere.
|
||||||
</Card>
|
</Card>
|
||||||
|
|||||||
@@ -79,11 +79,11 @@ gerbil:
|
|||||||
</Step>
|
</Step>
|
||||||
|
|
||||||
<Step title="Install Olm">
|
<Step title="Install Olm">
|
||||||
Use the generated credentials to install and configure Olm on your remote computer. See [Install Olm](/manage/clients/install-olm) for detailed instructions.
|
Use the generated credentials to install and configure Olm on your remote computer. See [Install Olm](/manage/clients/install-client) for detailed instructions.
|
||||||
</Step>
|
</Step>
|
||||||
|
|
||||||
<Step title="Configure resources">
|
<Step title="Configure resources">
|
||||||
Create [client resources](../resources/site-resources.mdx) for what you would like to access through the client. For example, to SSH into a server, create a resource like `22:localhost:22`.
|
Create [client resources](/manage/resources/client-resources.mdx) for what you would like to access through the client. For example, to SSH into a server, create a resource like `22:localhost:22`.
|
||||||
</Step>
|
</Step>
|
||||||
|
|
||||||
<Step title="Verify connection">
|
<Step title="Verify connection">
|
||||||
|
|||||||
@@ -6,7 +6,7 @@ description: "Learn how to use Pangolin's REST API to automate and script operat
|
|||||||
The API is REST-based and supports many operations available through the web interface. Authentication uses Bearer tokens, and you can create multiple API keys with specific permissions for different use cases.
|
The API is REST-based and supports many operations available through the web interface. Authentication uses Bearer tokens, and you can create multiple API keys with specific permissions for different use cases.
|
||||||
|
|
||||||
<Info>
|
<Info>
|
||||||
For Pangolin self-hosted, the integration API must be enabled. Check out [the documentation](../self-host/advanced/integration-api) for how to enable the integration API.
|
For Pangolin self-hosted, the integration API must be enabled. Check out [the documentation](/self-host/advanced/integration-api) for how to enable the integration API.
|
||||||
</Info>
|
</Info>
|
||||||
|
|
||||||
## Authentication
|
## Authentication
|
||||||
|
|||||||
@@ -612,7 +612,7 @@ This section contains the complete reference for all configuration options in `c
|
|||||||
**Example**: `postgresql://user:password@host:port/database`
|
**Example**: `postgresql://user:password@host:port/database`
|
||||||
|
|
||||||
<Note>
|
<Note>
|
||||||
See [PostgreSQL documentation](../database/postgres) for setup instructions.
|
See [PostgreSQL documentation](/self-host/advanced/database-options#postgresql) for setup instructions.
|
||||||
</Note>
|
</Note>
|
||||||
</ResponseField>
|
</ResponseField>
|
||||||
</Expandable>
|
</Expandable>
|
||||||
|
|||||||
@@ -119,7 +119,7 @@ service:
|
|||||||
|
|
||||||
<Warning>
|
<Warning>
|
||||||
Docker’s NAT-based port publishing feature automatically exposes all `ports:` defined in the `docker-compose` file on all network interfaces. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
|
Docker’s NAT-based port publishing feature automatically exposes all `ports:` defined in the `docker-compose` file on all network interfaces. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
|
||||||
Please see [complete warning about exposing ports](/Getting%20Started/dns-networking#ports-to-expose).
|
Please see [complete warning about exposing ports](/self-host/dns-and-networking).
|
||||||
</Warning>
|
</Warning>
|
||||||
|
|
||||||
7. Verify communication between the firewall bouncer and the CrowdSec container by running:
|
7. Verify communication between the firewall bouncer and the CrowdSec container by running:
|
||||||
|
|||||||
@@ -95,7 +95,7 @@ trusted_proxies:
|
|||||||
- VPS IP
|
- VPS IP
|
||||||
```
|
```
|
||||||
|
|
||||||
You also need to set up `Resource rules` in the pangolin dashboard. [See rule overview here](../03-Pangolin/05-bypass-rules.md).
|
You also need to set up `Resource rules` in the pangolin dashboard. [See rule overview here](/manage/access-control/bypass-rules).
|
||||||
|
|
||||||
Many thanks to steuerlexi for finding this out!
|
Many thanks to steuerlexi for finding this out!
|
||||||
|
|
||||||
|
|||||||
@@ -30,7 +30,7 @@ service:
|
|||||||
|
|
||||||
<Warning>
|
<Warning>
|
||||||
Docker’s NAT-based port publishing feature automatically exposes all `ports:` defined in `docker-compose` file. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
|
Docker’s NAT-based port publishing feature automatically exposes all `ports:` defined in `docker-compose` file. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
|
||||||
Please see [complete warning about exposing ports](/Getting%20Started/dns-networking#ports-to-expose).
|
Please see [complete warning about exposing ports](/self-host/dns-and-networking).
|
||||||
</Warning>
|
</Warning>
|
||||||
|
|
||||||
2. Update the `/config/traefik/traefik_config.yml` file to include the following:
|
2. Update the `/config/traefik/traefik_config.yml` file to include the following:
|
||||||
@@ -74,7 +74,7 @@ service:
|
|||||||
|
|
||||||
<Warning>
|
<Warning>
|
||||||
Docker’s NAT-based port publishing feature automatically exposes all `ports:` defined in the `docker-compose` file on all network interfaces. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
|
Docker’s NAT-based port publishing feature automatically exposes all `ports:` defined in the `docker-compose` file on all network interfaces. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
|
||||||
Please see [complete warning about exposing ports](/Getting%20Started/dns-networking#ports-to-expose).
|
Please see [complete warning about exposing ports](/self-host/dns-and-networking).
|
||||||
</Warning>
|
</Warning>
|
||||||
|
|
||||||
|
|
||||||
@@ -105,7 +105,7 @@ services:
|
|||||||
|
|
||||||
<Warning>
|
<Warning>
|
||||||
Docker’s NAT-based port publishing feature automatically exposes all `ports:` defined in the `docker-compose` file on all network interfaces. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
|
Docker’s NAT-based port publishing feature automatically exposes all `ports:` defined in the `docker-compose` file on all network interfaces. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
|
||||||
Please see [complete warning about exposing ports](/Getting%20Started/dns-networking#ports-to-expose).
|
Please see [complete warning about exposing ports](/self-host/dns-and-networking).
|
||||||
</Warning>
|
</Warning>
|
||||||
|
|
||||||
|
|
||||||
@@ -162,7 +162,7 @@ services:
|
|||||||
|
|
||||||
<Warning>
|
<Warning>
|
||||||
Docker’s NAT-based port publishing feature automatically exposes all `ports:` defined in the `docker-compose` file on all network interfaces. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
|
Docker’s NAT-based port publishing feature automatically exposes all `ports:` defined in the `docker-compose` file on all network interfaces. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
|
||||||
Please see [complete warning about exposing ports](/Getting%20Started/dns-networking#ports-to-expose).
|
Please see [complete warning about exposing ports](/self-host/dns-and-networking).
|
||||||
</Warning>
|
</Warning>
|
||||||
|
|
||||||
2. Start the Grafana container:
|
2. Start the Grafana container:
|
||||||
|
|||||||
@@ -4,7 +4,7 @@ description: "Learn how to convert your self-hosted Pangolin instance to a manag
|
|||||||
---
|
---
|
||||||
|
|
||||||
<Info>
|
<Info>
|
||||||
Check out the [Managed Deployment Guide](/self-host/managed-deployment) for more information on deploying a managed instance of Pangolin.
|
Check out the [Managed Deployment Guide](/self-host/quick-install-managed) for more information on deploying a managed instance of Pangolin.
|
||||||
</Info>
|
</Info>
|
||||||
|
|
||||||
## Who is this for?
|
## Who is this for?
|
||||||
|
|||||||
@@ -39,7 +39,7 @@ Files marked with `(*)` must be created manually. Volumes and other files are ge
|
|||||||
<Accordion title="Configuration Files">
|
<Accordion title="Configuration Files">
|
||||||
**`config/config.yml`**: Main Pangolin configuration file
|
**`config/config.yml`**: Main Pangolin configuration file
|
||||||
- Contains all Pangolin settings and options
|
- Contains all Pangolin settings and options
|
||||||
- See [Configuration Guide](/pangolin/configuration/config) for details
|
- See [Configuration Guide](/self-host/advanced/config-file) for details
|
||||||
|
|
||||||
**`config/traefik/traefik_config.yml`**: Traefik static configuration
|
**`config/traefik/traefik_config.yml`**: Traefik static configuration
|
||||||
- Global Traefik settings and entry points
|
- Global Traefik settings and entry points
|
||||||
|
|||||||
@@ -4,7 +4,7 @@ description: "Deploy managed Pangolin manually using Docker Compose without the
|
|||||||
---
|
---
|
||||||
|
|
||||||
<Tip>
|
<Tip>
|
||||||
This guide is for managed Pangolin. If you are looking for self-hosted Pangolin please see the [Docker Compose](self-host/docker-compose) guide.
|
This guide is for managed Pangolin. If you are looking for self-hosted Pangolin please see the [Docker Compose](/self-host/manual/docker-compose) guide.
|
||||||
</Tip>
|
</Tip>
|
||||||
|
|
||||||
This guide walks you through setting up Pangolin manually using Docker Compose without the automated installer. This approach gives you full control over the configuration and deployment process.
|
This guide walks you through setting up Pangolin manually using Docker Compose without the automated installer. This approach gives you full control over the configuration and deployment process.
|
||||||
@@ -39,7 +39,7 @@ Files marked with `(*)` must be created manually. Volumes and other files are ge
|
|||||||
<Accordion title="Configuration Files">
|
<Accordion title="Configuration Files">
|
||||||
**`config/config.yml`**: Main Pangolin configuration file
|
**`config/config.yml`**: Main Pangolin configuration file
|
||||||
- Contains all Pangolin settings and options
|
- Contains all Pangolin settings and options
|
||||||
- See [Configuration Guide](/pangolin/configuration/config) for details
|
- See [Configuration Guide](/self-host/advanced/config-file) for details
|
||||||
|
|
||||||
**`config/traefik/traefik_config.yml`**: Traefik static configuration
|
**`config/traefik/traefik_config.yml`**: Traefik static configuration
|
||||||
- Global Traefik settings and entry points
|
- Global Traefik settings and entry points
|
||||||
|
|||||||
@@ -46,7 +46,7 @@ Pangolin uses a yaml file for configuration. If this is not present on start up,
|
|||||||
|
|
||||||
Create a `config.yml` file in the `config` folder.
|
Create a `config.yml` file in the `config` folder.
|
||||||
|
|
||||||
See the [Configuration](/pangolin/configuration/config) section for what to put in this file.
|
See the [Configuration](/self-host/advanced/config-file) section for what to put in this file.
|
||||||
|
|
||||||
```
|
```
|
||||||
pangolin/
|
pangolin/
|
||||||
|
|||||||
Reference in New Issue
Block a user