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.

Sign up for GitHub

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

update high availability faq #457

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

update high availability faq #457

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 5 additions & 1 deletion crowdsec-docs/docs/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,7 +185,11 @@ $ sudo HTTP_PROXY=socks5://127.0.0.1:9050 HTTPS_PROXY=socks5://127.0.0.1:9050 cs

## How to setup High Availability for Local API

When setting up High Availability for Local API, do not forget to share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)
If you want to deploy CrowdSec in a high availability setup, you need this requirement:

- Using a shared database (PostgreSQL, MySQL, MariaDB, etc.) for storing decisions and alerts
- Each Local API instance should have unique online credentials to be able to push metrics
- Share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)

## How to disable the central API

Expand Down
6 changes: 5 additions & 1 deletion crowdsec-docs/versioned_docs/version-v1.0/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,11 @@ $ sudo HTTP_PROXY=socks5://127.0.0.1:9050 HTTPS_PROXY=socks5://127.0.0.1:9050 cs

## How to setup High Availability for Local API

When setting up High Availability for Local API, do not forget to share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)
If you want to deploy CrowdSec in a high availability setup, you need this requirement:

- Using a shared database (PostgreSQL, MySQL, MariaDB, etc.) for storing decisions and alerts
- Each Local API instance should have unique online credentials to be able to push metrics
- Share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)

## How to disable the central API

Expand Down
6 changes: 5 additions & 1 deletion crowdsec-docs/versioned_docs/version-v1.1/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,11 @@ $ sudo HTTP_PROXY=socks5://127.0.0.1:9050 HTTPS_PROXY=socks5://127.0.0.1:9050 cs

## How to setup High Availability for Local API

When setting up High Availability for Local API, do not forget to share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)
If you want to deploy CrowdSec in a high availability setup, you need this requirement:

- Using a shared database (PostgreSQL, MySQL, MariaDB, etc.) for storing decisions and alerts
- Each Local API instance should have unique online credentials to be able to push metrics
- Share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)

## How to disable the central API

Expand Down
6 changes: 5 additions & 1 deletion crowdsec-docs/versioned_docs/version-v1.2.2/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,7 +178,11 @@ $ sudo HTTP_PROXY=socks5://127.0.0.1:9050 HTTPS_PROXY=socks5://127.0.0.1:9050 cs

## How to setup High Availability for Local API

When setting up High Availability for Local API, do not forget to share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)
If you want to deploy CrowdSec in a high availability setup, you need this requirement:

- Using a shared database (PostgreSQL, MySQL, MariaDB, etc.) for storing decisions and alerts
- Each Local API instance should have unique online credentials to be able to push metrics
- Share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)

## How to disable the central API

Expand Down
6 changes: 5 additions & 1 deletion crowdsec-docs/versioned_docs/version-v1.2/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,11 @@ $ sudo HTTP_PROXY=socks5://127.0.0.1:9050 HTTPS_PROXY=socks5://127.0.0.1:9050 cs

## How to setup High Availability for Local API

When setting up High Availability for Local API, do not forget to share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)
If you want to deploy CrowdSec in a high availability setup, you need this requirement:

- Using a shared database (PostgreSQL, MySQL, MariaDB, etc.) for storing decisions and alerts
- Each Local API instance should have unique online credentials to be able to push metrics
- Share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)

## How to disable the central API

Expand Down
6 changes: 5 additions & 1 deletion crowdsec-docs/versioned_docs/version-v1.3.0/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,7 +178,11 @@ $ sudo HTTP_PROXY=socks5://127.0.0.1:9050 HTTPS_PROXY=socks5://127.0.0.1:9050 cs

## How to setup High Availability for Local API

When setting up High Availability for Local API, do not forget to share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)
If you want to deploy CrowdSec in a high availability setup, you need this requirement:

- Using a shared database (PostgreSQL, MySQL, MariaDB, etc.) for storing decisions and alerts
- Each Local API instance should have unique online credentials to be able to push metrics
- Share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)

## How to disable the central API

Expand Down
6 changes: 5 additions & 1 deletion crowdsec-docs/versioned_docs/version-v1.3.4/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,7 +178,11 @@ $ sudo HTTP_PROXY=socks5://127.0.0.1:9050 HTTPS_PROXY=socks5://127.0.0.1:9050 cs

## How to setup High Availability for Local API

When setting up High Availability for Local API, do not forget to share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)
If you want to deploy CrowdSec in a high availability setup, you need this requirement:

- Using a shared database (PostgreSQL, MySQL, MariaDB, etc.) for storing decisions and alerts
- Each Local API instance should have unique online credentials to be able to push metrics
- Share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)

## How to disable the central API

Expand Down
6 changes: 5 additions & 1 deletion crowdsec-docs/versioned_docs/version-v1.4.0/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,7 +178,11 @@ $ sudo HTTP_PROXY=socks5://127.0.0.1:9050 HTTPS_PROXY=socks5://127.0.0.1:9050 cs

## How to setup High Availability for Local API

When setting up High Availability for Local API, do not forget to share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)
If you want to deploy CrowdSec in a high availability setup, you need this requirement:

- Using a shared database (PostgreSQL, MySQL, MariaDB, etc.) for storing decisions and alerts
- Each Local API instance should have unique online credentials to be able to push metrics
- Share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)

## How to disable the central API

Expand Down
6 changes: 5 additions & 1 deletion crowdsec-docs/versioned_docs/version-v1.5.0/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,7 +185,11 @@ $ sudo HTTP_PROXY=socks5://127.0.0.1:9050 HTTPS_PROXY=socks5://127.0.0.1:9050 cs

## How to setup High Availability for Local API

When setting up High Availability for Local API, do not forget to share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)
If you want to deploy CrowdSec in a high availability setup, you need this requirement:

- Using a shared database (PostgreSQL, MySQL, MariaDB, etc.) for storing decisions and alerts
- Each Local API instance should have unique online credentials to be able to push metrics
- Share the same `CS_LAPI_SECRET` between your Local API instances : it is the secret used to signed JWT tokens. (By default it's generated from PRNG at startup)

## How to disable the central API

Expand Down