diff --git a/crowdsec-docs/docs/faq.md b/crowdsec-docs/docs/faq.md index ce1010112..7e83bde35 100644 --- a/crowdsec-docs/docs/faq.md +++ b/crowdsec-docs/docs/faq.md @@ -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 diff --git a/crowdsec-docs/versioned_docs/version-v1.0/faq.md b/crowdsec-docs/versioned_docs/version-v1.0/faq.md index e9214c311..dd535f2bc 100644 --- a/crowdsec-docs/versioned_docs/version-v1.0/faq.md +++ b/crowdsec-docs/versioned_docs/version-v1.0/faq.md @@ -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 diff --git a/crowdsec-docs/versioned_docs/version-v1.1/faq.md b/crowdsec-docs/versioned_docs/version-v1.1/faq.md index b2ad9a000..aa4ac1afc 100644 --- a/crowdsec-docs/versioned_docs/version-v1.1/faq.md +++ b/crowdsec-docs/versioned_docs/version-v1.1/faq.md @@ -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 diff --git a/crowdsec-docs/versioned_docs/version-v1.2.2/faq.md b/crowdsec-docs/versioned_docs/version-v1.2.2/faq.md index 81d88f56b..eacc57985 100644 --- a/crowdsec-docs/versioned_docs/version-v1.2.2/faq.md +++ b/crowdsec-docs/versioned_docs/version-v1.2.2/faq.md @@ -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 diff --git a/crowdsec-docs/versioned_docs/version-v1.2/faq.md b/crowdsec-docs/versioned_docs/version-v1.2/faq.md index b2ad9a000..aa4ac1afc 100644 --- a/crowdsec-docs/versioned_docs/version-v1.2/faq.md +++ b/crowdsec-docs/versioned_docs/version-v1.2/faq.md @@ -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 diff --git a/crowdsec-docs/versioned_docs/version-v1.3.0/faq.md b/crowdsec-docs/versioned_docs/version-v1.3.0/faq.md index 81d88f56b..eacc57985 100644 --- a/crowdsec-docs/versioned_docs/version-v1.3.0/faq.md +++ b/crowdsec-docs/versioned_docs/version-v1.3.0/faq.md @@ -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 diff --git a/crowdsec-docs/versioned_docs/version-v1.3.4/faq.md b/crowdsec-docs/versioned_docs/version-v1.3.4/faq.md index 81d88f56b..eacc57985 100644 --- a/crowdsec-docs/versioned_docs/version-v1.3.4/faq.md +++ b/crowdsec-docs/versioned_docs/version-v1.3.4/faq.md @@ -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 diff --git a/crowdsec-docs/versioned_docs/version-v1.4.0/faq.md b/crowdsec-docs/versioned_docs/version-v1.4.0/faq.md index 81d88f56b..eacc57985 100644 --- a/crowdsec-docs/versioned_docs/version-v1.4.0/faq.md +++ b/crowdsec-docs/versioned_docs/version-v1.4.0/faq.md @@ -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 diff --git a/crowdsec-docs/versioned_docs/version-v1.5.0/faq.md b/crowdsec-docs/versioned_docs/version-v1.5.0/faq.md index 12ef253fc..e6eb74ea0 100644 --- a/crowdsec-docs/versioned_docs/version-v1.5.0/faq.md +++ b/crowdsec-docs/versioned_docs/version-v1.5.0/faq.md @@ -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