fix: broken links

.gitlab-ci.yml

@@ -30,6 +30,8 @@ deploy_master:
     - master
   before_script:
     - NAMESPACE=ns-cpd-p01-syn
+    - echo $READ_REGISTRY_TOKEN
+    - echo $KUBE_CONFIG_CPD_PROD
     - export KUBECONFIG=$KUBE_CONFIG_CPD_PROD
   script:
     - oc create secret -n $NAMESPACE docker-registry forge-secret --docker-server=$CI_REGISTRY --docker-username=forge-secret --docker-password=$READ_REGISTRY_TOKEN --dry-run=client -o yaml | oc apply -f -

README.md

-# [Self Data Grandlyon Documentation](https://doc.self-data.alpha.grandlyon.com/)
+# [Self Data Grandlyon Documentation](https://doc.self-data.apps.grandlyon.com/)
 
 ## Install dependencies
 

docs/ecolyo/functionalities/dacc.md

@@ -236,7 +236,7 @@ All the data aggregated in the dacc can be visualized with a *Metabase* website
 
 ## Errors
 
-More here in [DJU](https://doc.self-data.alpha.grandlyon.com/ecolyo/functionalities/profile_type/).
+More here in [DJU](/ecolyo/functionalities/profile_type/#dju).
 
 If there is an authentication error, the api will returns an error in html format to cozy, so you'll get from cozy an error 502 as following, because cozy expects a json response :
 

docs/ecolyo/functionalities/onboarding.md

@@ -12,7 +12,7 @@ When the user connects for the first time to Ecolyo, onboarding screens will be
 
 First of all, we display the GCU screen, which allows user to read the General Condition of Use and the Legal Notice. The user should consent to all the terms to go further in the application.
 !!! note "About terms"
-    More details are available on the [term section](/ecolyo/functionalities/terms.md).
+    More details are available on the [term section](/ecolyo/functionalities/terms).
 
 ### Welcome modal
 

docs/ecolyo/functionalities/usage_events_tracking.md

@@ -52,7 +52,7 @@ Once the indicators is calculated we will:
 
 At the end of the service, the service will change the _aggregated_ flag to **true** for all events present in the array.
 
-More technical information are available [here](/ecolyo/services/aggregator_usage_events.md)
+More technical information are available [here](/ecolyo/technical/services/aggregator_usage_events)
 
 ## Remote doctype
 

docs/ecolyo/technical/services/aggregator_usage_events.md

@@ -23,7 +23,7 @@ The service is responsible of :
 As the remote doctype is not yet available for the service here are the remaining task to do:
 
 - In the manifest.webapp:
-    - Declare the remote doctype [see here](/ecolyo/project_architecture/remote_doctypes.md)
+    - Declare the remote doctype [see here](/ecolyo/technical/remote_doctypes)
     - Define the cron to run every day: to check with cozy to ensure that all instances will not trigger the service at the same time
     - Create the translation for "fr" and "en"
 - In the service:

docs/pilote/Pilote-Usager/functionalities/cozy-registry.md

@@ -18,7 +18,7 @@ A service is run every day to send instance information to the registry.
 ## Launch the service locally
 
 - Switch to Node 16 (using nvm or n)
-- install local remote doctypes (details [here](https://doc.self-data.alpha.grandlyon.com/ecolyo/project_architecture/remote_doctypes/#local-remote-doctype)), add a folder named org.mps.registry.dev, inside it add a file named request with the following content :
+- install local remote doctypes (details [here](/ecolyo/project_architecture/remote_doctypes/#local-remote-doctype)), add a folder named org.mps.registry.dev, inside it add a file named request with the following content :
 
 ```
 POST https://cozy-registry.poc.self-data.alpha.grandlyon.com/api/pilote