fix broken links pointing to unversioned doc

clementAC · clementAC · commit 43b4b3f079b8 · 2024-10-31T18:09:16.000+01:00
diff --git a/crowdsec-docs/docs/appsec/installation.md b/crowdsec-docs/docs/appsec/installation.md
@@ -104,11 +104,11 @@ tcp        0      0 127.0.0.1:7422          0.0.0.0:*               LISTEN
 
 Configuring the AppSec component [accross remediation components](appsec/installation.md#pre-requisites) can vary:
 
-| Name      | Minimum Version | Public Doc |
-| --------- | --------------- | ----------- |
-| nginx     | 1.0.6rc         | [Public Doc](/u/bouncers/nginx#application-security-component-configuration) |
-| openresty | 1.0.1rc         | [Public Doc](/u/bouncers/openresty#application-security-component-configuration) |
-| traefik | 1.2.0 | [Public Doc](https://github.com/maxlerebourg/crowdsec-bouncer-traefik-plugin/blob/main/examples/appsec-enabled/README.md) |
+| Name      | Minimum Version | Public Doc                                                                                                                |
+| --------- | --------------- | ------------------------------------------------------------------------------------------------------------------------- |
+| nginx     | 1.0.6rc         | [Public Doc](/u/bouncers/nginx#application-security-component-configuration)                                              |
+| openresty | 1.0.1rc         | [Public Doc](/u/bouncers/openresty#application-security-component-configuration)                                          |
+| traefik   | 1.2.0           | [Public Doc](https://github.com/maxlerebourg/crowdsec-bouncer-traefik-plugin/blob/main/examples/appsec-enabled/README.md) |
 
 
 :::info
@@ -138,4 +138,4 @@ And if we look at it in a browser, the user is presented with the HTML page emit
 ## Et Voila !
 
 Your application should now be protected from the most common exploitation attempts.  
-[If you have already enrolled your instance in the console](/docs/next/console/enrollment), you will see alerts appearing there too!
+[If you have already enrolled your instance in the console](/u/getting_started/post_installation/console#engines-page), you will see alerts appearing there too!
diff --git a/crowdsec-docs/docs/getting_started/install_opnsense.md b/crowdsec-docs/docs/getting_started/install_opnsense.md
@@ -27,7 +27,7 @@ Do not enable/start the services from the terminal like you would on a standard
 
 Refresh the page and go to `Services > CrowdSec > Overview` to verify the running services and installed configurations.
 
-Great, you now have CrowdSec installed on your system. Have a look at the [post installation steps](/getting_started/next_steps.md) to see how to to configure and optimize it,
+Great, you now have CrowdSec installed on your system. Have a look at the [post installation steps](/u/getting_started/next_steps) to see how to to configure and optimize it,
 these recommendations are valid for any system.
 
 
diff --git a/crowdsec-docs/docs/getting_started/install_pyagent.md b/crowdsec-docs/docs/getting_started/install_pyagent.md
@@ -82,7 +82,7 @@ decisions = client.get_decisions(
 
 ```
 
-To obtain attachment key for enrolling a machine see [this doc](../console/enrollment/#where-can-i-find-my-enrollment-key) 
+To obtain attachment key for enrolling a machine see [this doc](/u/getting_started/post_installation/console/#engines-page) 
 
 See reference section for more details. 
 
diff --git a/crowdsec-docs/src/components/HomepageFeatures.js b/crowdsec-docs/src/components/HomepageFeatures.js
@@ -18,7 +18,7 @@ const FeatureList = [
     //screenshot metabase ?
     title: 'Replayable',
     Svg: require('../../static/img/icon-replay.svg').default,
-    link: "/docs/user_guides/replay_mode",
+    link: "/u/user_guides/replay_mode",
     description: (
       <>
         CrowdSec is able to process both live and old logs, which makes it false-positive resilient. 
diff --git a/crowdsec-docs/unversioned/bouncers/fastly.mdx b/crowdsec-docs/unversioned/bouncers/fastly.mdx
@@ -26,7 +26,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
 # cs-fastly-bouncer
 
 A Remediation Component that syncs the decisions made by CrowdSec with Fastly's VCL. Manages multi account, multi service setup. Supports IP, Country and AS scoped decisions.
-To learn how to setup crowdsec to consume fastly logs see [this](/docs/next/user_guides/consuming_fastly_logs)
+To learn how to setup crowdsec to consume fastly logs see [this](/u/user_guides/consuming_fastly_logs)
 
 
 # Installation:
diff --git a/crowdsec-docs/unversioned/console/blocklists/integrations/firewall.md b/crowdsec-docs/unversioned/console/blocklists/integrations/firewall.md
@@ -21,7 +21,7 @@ In the next step, we will provide the necessary details for retrieving the IP ad
 
 ## Use an integration
 
-| Don't forgot to [subscribe to a blocklist](/u/console/blocklists/subscription/#subscribe-a-firewall-integration-to-a-blocklist) to make the integration useful.
+| Don't forgot to [subscribe to a blocklist](/u/console/blocklists/subscription/#integrations) to make the integration useful.
 
 Every product product has its way to handle external blocklists. We provide a simple URL to retrieve the IPs in a format that suits your needs. You can find the supported provider documentations and output format examples in the following array.
 
diff --git a/crowdsec-docs/unversioned/console/security_engines/dashboard.md b/crowdsec-docs/unversioned/console/security_engines/dashboard.md
@@ -24,9 +24,9 @@ Each Security Engine has a card that displays essential details to facilitate mo
 - **Name**: Clicking on the name will redirect to the detailed page of the Security Engine.
 - **IP**: Clicking on the IP will copy it to the clipboard.
 - **Enroll Date**
-- **Tags**: Add custom tags to the engines by using the ["doc"](/console/security_engines/name_and_tags.md) tag format.
+- **Tags**: Add custom tags to the engines by using the ["doc"](/u/console/security_engines/name_and_tags) tag format.
 - **Alerts / Scenarios / Remediation Components / Blocklists / Log Processors (Distributed Setup only)**: Clicking any items will redirect to a dedicated section with relevant information.
-- **Activity**: This feature helps focus on Security Engines that require your attention. The ["Troubleshoot"](/console/security_engines/troubleshooting.md) feature can identify problems in your stack by analyzing past engine activity.
+- **Activity**: This feature helps focus on Security Engines that require your attention. The ["Troubleshoot"](/u/console/security_engines/troubleshooting) feature can identify problems in your stack by analyzing past engine activity.
 - **Distributed Setup**: These are considered Distributed Setup Engines when multiple log processors are attached. [(Get more info here)](/docs/next/getting_started/security_engine_intro/#why-is-my-security-engine-classed-as-a-log-processor-within-the-console)
 
 ### Basic Card
diff --git a/crowdsec-docs/unversioned/console/security_engines/details_page.md b/crowdsec-docs/unversioned/console/security_engines/details_page.md
@@ -13,7 +13,7 @@ This page will reference information about a specific Security Engine. This page
 
 ### Summary
 
-At the top of the page, the essential information regarding the Security Engine is referenced. This includes the IP address, ID, last activity, tags, and the current version. This page will notify if the Security Engine is not running the latest CrowdSec version. To identify outdated Security Engines, you can also utilize the [**Troubleshooting**](/console/security_engines/troubleshooting) feature.
+At the top of the page, the essential information regarding the Security Engine is referenced. This includes the IP address, ID, last activity, tags, and the current version. This page will notify if the Security Engine is not running the latest CrowdSec version. To identify outdated Security Engines, you can also utilize the [**Troubleshooting**](/u/console/security_engines/troubleshooting) feature.
 
 ![Security Engine details page](/img/console/security_engines/details-page-summary.png)
 
diff --git a/crowdsec-docs/unversioned/console/security_engines/select_multiple_organizations.md b/crowdsec-docs/unversioned/console/security_engines/select_multiple_organizations.md
@@ -27,7 +27,7 @@ To use the multi organization selection, these steps should be followed:
 
 ![Select multiple organizations modal](/img/console/security_engines/select-multiple-organizations-list.png)
 
-The [**"Troubleshooting"**](/console/security_engines/troubleshooting) feature is also applied to multiple organizations. Allowing us to find issues directly across all selected organizations.
+The [**"Troubleshooting"**](/u/console/security_engines/troubleshooting) feature is also applied to multiple organizations. Allowing us to find issues directly across all selected organizations.
 
 ![Select multiple organizations modal](/img/console/security_engines/select-multiple-organizations-troubleshooting.png)
 
diff --git a/crowdsec-docs/unversioned/getting_started/installation/whm.mdx b/crowdsec-docs/unversioned/getting_started/installation/whm.mdx
@@ -137,7 +137,7 @@ You can restart your CrowdSec instance after confirmation to force a refresh of
 
 ![Enrolled_SE](/img/whm-console-example.png)
 
-Check some of the console features in the [Console section](https://docs.crowdsec.net/docs/next/console/intro)
+Check some of the console features in the [Console section](https://docs.crowdsec.net/u/console/intro)
 
 ## Troubleshoot
 
diff --git a/crowdsec-docs/unversioned/troubleshooting/intro.md b/crowdsec-docs/unversioned/troubleshooting/intro.md
@@ -212,7 +212,7 @@ This command will allow you to see each parser behavior.
 
 :::warning
 Do **not** use `cscli explain` on big log files, as this command will buffer a lot of information in memory to achieve this.
-If you want to check crowdsec's behaviour on big log files, please see [replay mode](/docs/next/user_guides/replay_mode/).
+If you want to check crowdsec's behaviour on big log files, please see [replay mode](/u/user_guides/replay_mode/).
 :::
 
 ### I want to add collection X : how to add log files, and how to test if it works ?
diff --git a/crowdsec-docs/unversioned/troubleshooting/security_engine.mdx b/crowdsec-docs/unversioned/troubleshooting/security_engine.mdx
@@ -132,7 +132,7 @@ Please review your acquisition files and remove any duplicate log entires.
 
 ### Is scenario X working on my logs ?
 
-You can replay old logs with [replay mode](/docs/next/user_guides/replay_mode/), which will allow you to see which scenarios would have been triggered. If no scenario seem to trigger, you can have a closer look at potential parsing errors with [`cscli explain`](/docs/next/cscli/cscli_explain).
+You can replay old logs with [replay mode](/u/user_guides/replay_mode/), which will allow you to see which scenarios would have been triggered. If no scenario seem to trigger, you can have a closer look at potential parsing errors with [`cscli explain`](/docs/next/cscli/cscli_explain).
 
 ## Configuration
 
@@ -162,7 +162,7 @@ SQLite by default as it's suitable for standalone/single-engine setups.
 
 ### Multi-server setup
 
-For multi-server setup please follow our guides on [distributed architecture](/docs/next/distributed_architecture/intro).
+For multi-server setup please follow our guides on [distributed architecture](/u/user_guides/multiserver_setup).
 
 ## Logs
 
diff --git a/crowdsec-docs/versioned_docs/version-v1.3.4/troubleshooting.md b/crowdsec-docs/versioned_docs/version-v1.3.4/troubleshooting.md
@@ -75,7 +75,7 @@ time="19-04-2022 15:43:07" level=error msg="API error: access forbidden"
 
 ## My scenario is triggered with less logs than the scenario capacity
 
-During the installation, the CrowdSec [Wizard](/docs/user_guides/building#using-the-wizard) is ran, which detects the basic logs files to add in the [acquisition](/docs/concepts#acquisition) configuration.
+During the installation, the CrowdSec [Wizard](/u/user_guides/building#using-the-wizard) is ran, which detects the basic logs files to add in the [acquisition](/docs/concepts#acquisition) configuration.
 If you re-run the `wizard.sh` script after the installation and you have common log files, they might be set up multiple times in your acquisition configuration. This means that CrowdSec will read each logs line as many time as you have the logs file configured in your acquisition configuration.
 
 
@@ -151,12 +151,12 @@ This command will allow you to see each parser behaviour.
 
 :::warning
 Do **not** use `cscli explain` on big log files, as this command will buffer a lot of information in memory to achieve this.
-If you want to check crowdsec's behaviour on big log files, please see [replay mode](/docs/user_guides/replay_mode/).
+If you want to check crowdsec's behaviour on big log files, please see [replay mode](/u/user_guides/replay_mode/).
 :::
 
 ## Is scenario XXX working on my logs ?
 
-You can replay old logs with [replay mode](/docs/user_guides/replay_mode/), which will allow you to see which scenarios would have been triggered. If no scenario seem to trigger, you can have a closer look at potential parsing errors with [`cscli explain`](/docs/cscli/cscli_explain).
+You can replay old logs with [replay mode](/u/user_guides/replay_mode/), which will allow you to see which scenarios would have been triggered. If no scenario seem to trigger, you can have a closer look at potential parsing errors with [`cscli explain`](/docs/cscli/cscli_explain).
 
 
 ## I want to add collection XXX : how to add log files, and how to test if it works ?
diff --git a/crowdsec-docs/versioned_docs/version-v1.4.0/troubleshooting.md b/crowdsec-docs/versioned_docs/version-v1.4.0/troubleshooting.md
@@ -75,7 +75,7 @@ time="19-04-2022 15:43:07" level=error msg="API error: access forbidden"
 
 ## My scenario is triggered with less logs than the scenario capacity
 
-During the installation, the CrowdSec [Wizard](/docs/user_guides/building#using-the-wizard) is ran, which detects the basic logs files to add in the [acquisition](/docs/concepts#acquisition) configuration.
+During the installation, the CrowdSec [Wizard](/u/user_guides/building#using-the-wizard) is ran, which detects the basic logs files to add in the [acquisition](/docs/concepts#acquisition) configuration.
 If you re-run the `wizard.sh` script after the installation and you have common log files, they might be set up multiple times in your acquisition configuration. This means that CrowdSec will read each logs line as many time as you have the logs file configured in your acquisition configuration.
 
 
@@ -151,12 +151,12 @@ This command will allow you to see each parser behaviour.
 
 :::warning
 Do **not** use `cscli explain` on big log files, as this command will buffer a lot of information in memory to achieve this.
-If you want to check crowdsec's behaviour on big log files, please see [replay mode](/docs/user_guides/replay_mode/).
+If you want to check crowdsec's behaviour on big log files, please see [replay mode](/u/user_guides/replay_mode/).
 :::
 
 ## Is scenario XXX working on my logs ?
 
-You can replay old logs with [replay mode](/docs/user_guides/replay_mode/), which will allow you to see which scenarios would have been triggered. If no scenario seem to trigger, you can have a closer look at potential parsing errors with [`cscli explain`](/docs/cscli/cscli_explain).
+You can replay old logs with [replay mode](/u/user_guides/replay_mode/), which will allow you to see which scenarios would have been triggered. If no scenario seem to trigger, you can have a closer look at potential parsing errors with [`cscli explain`](/docs/cscli/cscli_explain).
 
 
 ## I want to add collection XXX : how to add log files, and how to test if it works ?
diff --git a/crowdsec-docs/versioned_docs/version-v1.5.0/troubleshooting.md b/crowdsec-docs/versioned_docs/version-v1.5.0/troubleshooting.md
@@ -107,7 +107,7 @@ Bouncers configuration files by default are located in:
 
 ## My scenario is triggered with less logs than the scenario capacity
 
-During the installation, the CrowdSec [Wizard](/docs/user_guides/building#using-the-wizard) is ran, which detects the basic logs files to add in the [acquisition](/docs/concepts#acquisition) configuration.
+During the installation, the CrowdSec [Wizard](/u/user_guides/building#using-the-wizard) is ran, which detects the basic logs files to add in the [acquisition](/docs/concepts#acquisition) configuration.
 If you re-run the `wizard.sh` script after the installation and you have common log files, they might be set up multiple times in your acquisition configuration. This means that CrowdSec will read each logs line as many time as you have the logs file configured in your acquisition configuration.
 
 
@@ -183,12 +183,12 @@ This command will allow you to see each parser behaviour.
 
 :::warning
 Do **not** use `cscli explain` on big log files, as this command will buffer a lot of information in memory to achieve this.
-If you want to check crowdsec's behaviour on big log files, please see [replay mode](/docs/user_guides/replay_mode/).
+If you want to check crowdsec's behaviour on big log files, please see [replay mode](/u/user_guides/replay_mode/).
 :::
 
 ## Is scenario XXX working on my logs ?
 
-You can replay old logs with [replay mode](/docs/user_guides/replay_mode/), which will allow you to see which scenarios would have been triggered. If no scenario seem to trigger, you can have a closer look at potential parsing errors with [`cscli explain`](/docs/cscli/cscli_explain).
+You can replay old logs with [replay mode](/u/user_guides/replay_mode/), which will allow you to see which scenarios would have been triggered. If no scenario seem to trigger, you can have a closer look at potential parsing errors with [`cscli explain`](/docs/cscli/cscli_explain).
 
 
 ## I want to add collection XXX : how to add log files, and how to test if it works ?
diff --git a/crowdsec-docs/versioned_docs/version-v1.6.0/appsec/installation.md b/crowdsec-docs/versioned_docs/version-v1.6.0/appsec/installation.md
@@ -166,4 +166,4 @@ And if we look at it in a browser, the user is presented with the HTML page emit
 ## Et Voila !
 
 Your application should now be protected from the most common exploitation attempts.  
-[If you have already enrolled your instance in the console](/docs/next/console/enrollment), you will see alerts appearing there too!
+[If you have already enrolled your instance in the console](/u/getting_started/post_installation/console#engines-page), you will see alerts appearing there too!
diff --git a/crowdsec-docs/versioned_docs/version-v1.6.0/getting_started/install_pyagent.md b/crowdsec-docs/versioned_docs/version-v1.6.0/getting_started/install_pyagent.md
@@ -6,7 +6,7 @@ sidebar_position: 1
 
 # Using our Python SDK
 
-This python SDK is designed for signal sharing partners to send signals and benefit from the community blocklist. Learn more about [signal sharing](TODO).
+This python SDK is designed for signal sharing partners to send signals and benefit from the community blocklist. <!-- Learn more about [signal sharing](TODO). -->
 
 Our SDK does the heavy lifting of the CAPI connectivity so you can simply, sendSignals and getDecisions, as well as enroll your soft-agent into the console.
 
@@ -82,7 +82,7 @@ decisions = client.get_decisions(
 
 ```
 
-To obtain attachment key for enrolling a machine see [this doc](../console/enrollment/#where-can-i-find-my-enrollment-key) 
+To obtain attachment key for enrolling a machine see [this doc](/u/getting_started/post_installation/console/#engines-page) 
 
 See reference section for more details. 
 
