From 35d9c89047e7fa99c8df08703fcb17a17d3ee7dd Mon Sep 17 00:00:00 2001 From: ilbertt Date: Wed, 22 Oct 2025 18:52:27 +0200 Subject: [PATCH] docs: update canister environment guide --- docs/src/content/docs/canister-environment.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/content/docs/canister-environment.mdx b/docs/src/content/docs/canister-environment.mdx index 74165549a..6ab2e7be2 100644 --- a/docs/src/content/docs/canister-environment.mdx +++ b/docs/src/content/docs/canister-environment.mdx @@ -47,7 +47,7 @@ sequenceDiagram The flow is the following: 1. The developer deploys the backend canister. -2. The developer sets the `PUBLIC_CANISTER_ID:backend` environment variable to the backend canister ID via the management canister. +2. The developer sets the `PUBLIC_CANISTER_ID:backend` environment variable and its value (the backend canister ID) in the asset canister using the [management canister](https://internetcomputer.org/docs/references/system-canisters/management-canister). 3. The browser of the end user requests the HTML assets from the asset canister. 4. The asset canister serves the HTML assets with the `ic_env` cookie. In this example, it serves the `ic_root_key` (by default, see [below](#the-ic_env-cookie)) and `PUBLIC_CANISTER_ID:backend` variables. 5. The browser of the end user decodes the `ic_env` cookie and configures the actor with the root key and `PUBLIC_CANISTER_ID:backend` variables.