markdown source builds

Auto-generated via `{sandpaper}` Source : e34fc01 Branch : main Author : Frank Martin <[email protected]> Time : 2024-10-22 12:14:47 +0000 Message : Merge pull request #162 from vantage6/ch6_241017 Update chapter6 based on workshop feedback
vantage6 · Oct 22, 2024 · 6992c1b · 6992c1b
1 parent f1fbf6e
commit 6992c1b
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 11 deletions.
diff --git a/chap6_setup_node.md b/chap6_setup_node.md
@@ -556,29 +556,23 @@ When you finish the process, the node configuration file will be updated with th
 
 To make the new API key effective, you need to restart the node by running the command `v6 node stop` and then `v6 node start`.
 
-::::::::::::::::::::::::::::::::::::::::::::::::::::::: instructor
-Regarding challenge 3, it's important to mention that usually you cannot reset the API key of a node of an organization the user is not part of, even if it's in the same collaboration.
-:::::::::::::::::::::::::::::::::::::::::::::::::::::::
-
 ::::::::::::::::::::::::::::::::::::: challenge
 
 ## Challenge 3: Update the API key of a node
 
-1. Reset the API key of the node `node2` you created in the first exercise.
-2. Update the API key of the node `node2`, WITHOUT using the `v6 node set-api-key` command.
-3. How do you verify that the new API key is effective?
+1. Update the API key of the node `node1`, WITHOUT using the `v6 node set-api-key` command.
+2. How do you verify that the new API key is effective?
 
 ::: solution
 
-1. You can go to the `Nodes` tab in the administration page, then click on the tab of the node you want to reset the API key for, and click on the `Reset API key` button.
-2. We can update the API key in the configuration file:
+1. We can update the API key in the configuration file:
 
 - Run the `v6 node files` command to locate the configuration file.
 - Open the configuration file and write the new API key in the `api_key` field.
 - Stop the node with the `v6 node stop` command.
 - Restart the node with the `v6 node start` command.
 
-3. In order to verify the effectiveness of the API key change, we can restart the node with active logging:
+2. In order to verify the effectiveness of the API key change, we can restart the node with active logging:
 
 ```bash
 v6 node start --attach

diff --git a/md5sum.txt b/md5sum.txt
@@ -10,7 +10,7 @@
 "episodes/chap3_run_analysis_ui.md" "13437844ff6a365ad366278202c4d909" "site/built/chap3_run_analysis_ui.md" "2024-10-15"
 "episodes/chap4_manage_via_ui.md" "2cb4a6e763979b8509664aaa96a27401" "site/built/chap4_manage_via_ui.md" "2024-09-24"
 "episodes/chap5_python_client.md" "7db76eb5e2127b3088e5a6224554c9a6" "site/built/chap5_python_client.md" "2024-10-03"
-"episodes/chap6_setup_node.md" "096e6723dda07f48836005632754680b" "site/built/chap6_setup_node.md" "2024-10-04"
+"episodes/chap6_setup_node.md" "cc1ba8fb7b98a0f1efaad66d16042fc7" "site/built/chap6_setup_node.md" "2024-10-22"
 "episodes/chap7_algo_dev.md" "2384e305ae51d9bedfd594501b06358a" "site/built/chap7_algo_dev.md" "2024-10-02"
 "episodes/chap8_own_project.md" "62bb31ad244046349ef058e2eda2c15b" "site/built/chap8_own_project.md" "2024-10-02"
 "instructors/instructor-notes.md" "cae72b6712578d74a49fea7513099f8c" "site/built/instructor-notes.md" "2023-03-16"