chore: add aliases to cht sync pages (#1641)

medic · Oct 23, 2024 · 9990b05 · 9990b05
1 parent b561d1b
commit 9990b05
Show file tree

Hide file tree

Showing 7 changed files with 9 additions and 1 deletion.
diff --git a/content/en/hosting/analytics/_index.md b/content/en/hosting/analytics/_index.md
@@ -9,6 +9,8 @@ relatedContent: >
 aliases:
     - /apps/guides/data/analytics/
     - /apps/guides/data/analytics/introduction
+    - /building/guides/data/analytics/
+    - /building/guides/data/analytics/introduction
 ---
 
 {{% pageinfo %}}

diff --git a/content/en/hosting/analytics/building-dbt-models.md b/content/en/hosting/analytics/building-dbt-models.md
@@ -9,6 +9,7 @@ relatedContent: >
   building/reference/app-settings/hierarchy
 aliases:
    - /apps/guides/data/analytics/building-dbt-models
+   - /building/guides/data/analytics/building-dbt-models
 ---
 
 ## Overview

diff --git a/content/en/hosting/analytics/couch2pg-to-cht-sync-migration.md b/content/en/hosting/analytics/couch2pg-to-cht-sync-migration.md
@@ -9,6 +9,7 @@ relatedContent: >
   core/overview/data-flows-for-analytics/
 aliases:
    - /apps/guides/data/analytics/couch2pg-to-cht-sync-migration
+   - /building/guides/data/analytics/couch2pg-to-cht-sync-migration
 ---
 
 This page outlines guidelines for migrating from [couch2pg](https://github.com/medic/cht-couch2pg) to the data pipeline based on [CHT Sync](https://github.com/medic/cht-sync). One of the main changes in this flow is separating the syncing process from the data transformation, with dbt now handling the latter in [cht-pipeline](https://github.com/medic/cht-pipeline/). This migration requires dbt models in the cht-pipeline repository instead of SQL views and tables. One thing to note is that the schema for CHT Sync differs from cht-couch2pg, so dbt models will not directly replace the SQL views and tables. For instructions on how to get started with dbt models, refer to the [dbt models guide]({{< relref "hosting/analytics/testing-dbt-models" >}}).

diff --git a/content/en/hosting/analytics/environment-variables.md b/content/en/hosting/analytics/environment-variables.md
@@ -6,6 +6,7 @@ description: >
   Environment variables for running CHT Sync 
 aliases:
    - /apps/guides/data/analytics/environment-variables
+   - /building/guides/data/analytics/environment-variables
 ---
 
 There are two environment variable groups in the `.env` file (if using Docker Compose), or in the `values.yaml` file (if using Kubernetes). To successfully set up CHT Sync, it is important to understand the difference between them.

diff --git a/content/en/hosting/analytics/setup-docker-compose.md b/content/en/hosting/analytics/setup-docker-compose.md
@@ -9,6 +9,7 @@ relatedContent: >
   core/overview/cht-sync
 aliases:
    - /apps/guides/data/analytics/setup
+   - /building/guides/data/analytics/setup
 ---
 
 This guide will walk you through setting up a deployment of CHT Sync with the CHT using Docker. This path is recommended if you host the [CHT with Docker]({{< relref "hosting/4.x/production/docker" >}}).

diff --git a/content/en/hosting/analytics/setup-kubernetes.md b/content/en/hosting/analytics/setup-kubernetes.md
@@ -8,7 +8,8 @@ relatedContent: >
   core/overview/architecture
   core/overview/cht-sync
 aliases:
-   - /apps/guides/data/analytics/production
+    - /apps/guides/data/analytics/production
+    - /building/guides/data/analytics/production
 ---
 
 This guide will walk you through setting up a deployment of CHT Sync with the CHT using Kubernetes. This path is recommended if you already have a Kubernetes cluster [hosting the CHT]({{< relref "hosting/4.x/production/kubernetes" >}}).

diff --git a/content/en/hosting/analytics/testing-dbt-models.md b/content/en/hosting/analytics/testing-dbt-models.md
@@ -6,6 +6,7 @@ description: >
   Guide for testing dbt models
 aliases:
    - /apps/guides/data/analytics/testing-dbt-models
+   - /building/guides/data/analytics/testing-dbt-models
 ---
 
 ## Overview