diff --git a/docs/guide/bigquery.md b/docs/guide/bigquery.md index a9bfacae..f3921417 100644 --- a/docs/guide/bigquery.md +++ b/docs/guide/bigquery.md @@ -88,7 +88,7 @@ In this section, we will explore various BigQuery operations. With Runme features, you can successfully run and display your query's output, formatting it into a table for easy navigation. -To do this, you first need to set your `FORMAT`. Using [Runme’s environment variable](/configuration/cell-level#set-environment-variables), you will be prompted to set the `FORMAT`. Run the command below in your code cell. +To do this, you first need to set your `FORMAT`. Using [Runme’s environment variable](/configuration/cell-level#environment-variables), you will be prompted to set the `FORMAT`. Run the command below in your code cell. ```sh {"id":"01J2KDSN92SZZYTSN11D7GS2G9"} export FORMAT="json" diff --git a/docs/guide/cloud-render/cloud-run.md b/docs/guide/cloud-render/cloud-run.md index 80e1706f..98307ff4 100644 --- a/docs/guide/cloud-render/cloud-run.md +++ b/docs/guide/cloud-render/cloud-run.md @@ -6,7 +6,7 @@ title: Google Cloud Run Runme Cloud Renderers enable you to access various cloud resources directly within your Markdown files without the need to log into your cloud console. With Cloud Renderers, you can manage your Google Cloud Run resources and perform various operations without leaving your Markdown environment. -It is available on Runme client interfaces, including the [editor](/installation/vscode) and [web browser](/installation/web). This section will explore how you can access the Google Cloud Run with Runme Cloud Renderers in a [web browser](/installation/web.md). +It is available on Runme client interfaces, including the [editor](/installation/vscode) and [web browser](/installation/web). This section will explore how you can access the Google Cloud Run with Runme Cloud Renderers in a [web browser](/installation/web). ## Prerequisites @@ -34,7 +34,7 @@ mkdir my_new_directory Where `my_new_directory` is the name of your folder. -Now, navigate into that directory by [changing directory](/configuration/cell-level#cells-current-working-directory) to `my_new_directory`. +Now, navigate into that directory by [changing directory](/configuration/cell-level#cell-cwd-current-working-directory) to `my_new_directory`. - **Open the Web Browser** diff --git a/docs/guide/docker.md b/docs/guide/docker.md index 2e9a8426..4a259e44 100644 --- a/docs/guide/docker.md +++ b/docs/guide/docker.md @@ -286,7 +286,7 @@ docker rm $CONTAINER_ID_TEST Docker Compose is a tool for defining and running multi-container Docker applications. It uses YAML files to configure the application’s services and performs the creation and setup process for all the containers. -For this example, we created a [YAML file](https://github.com/stateful/blog-examples/blob/T-doc-notebook/docker-notebook/compose.yaml) to demonstrate how docker-compose works. If your YAML file is in a different directory from your current working directory, you can easily [change your Runme cell](/configuration/cell-level#cells-current-working-directory) to the directory where the file exists and then run the docker-compose command. +For this example, we created a [YAML file](https://github.com/stateful/blog-examples/blob/T-doc-notebook/docker-notebook/compose.yaml) to demonstrate how docker-compose works. If your YAML file is in a different directory from your current working directory, you can easily [change your Runme cell](/configuration/cell-level#cell-cwd-current-working-directory) to the directory where the file exists and then run the docker-compose command. ![docker-compose](/img/guide-page/dockerr-compose.png) diff --git a/docs/guide/foyle.md b/docs/guide/foyle.md index b804f8b6..87b4a06b 100644 --- a/docs/guide/foyle.md +++ b/docs/guide/foyle.md @@ -40,7 +40,7 @@ foyle config set openai.apiKeyFile=/path/to/openai/apikey 2. **Start the Server** -Run the command below to start the Foyle server on your local machine. However, you must ensure your API Key is in the directory where this command will run. If it isn’t, you can set the directory of your code cell to the directory where your API Key is located using the [CWD feature of Runme](/configuration/cell-level#cells-current-working-directory). +Run the command below to start the Foyle server on your local machine. However, you must ensure your API Key is in the directory where this command will run. If it isn’t, you can set the directory of your code cell to the directory where your API Key is located using the [CWD feature of Runme](/configuration/cell-level#cell-cwd-current-working-directory). ```sh {"background":"true","id":"01J331ERREM6TZ2VCVES792H65"} foyle serve @@ -145,7 +145,7 @@ Now that logging is enabled, you can verify that logs are being written and iden To view the logs, you need to follow the steps below; -- Create a new code cell block using Runme's [CWD feature](/configuration/cell-level#cells-current-working-directory) and configure the path for that code cell block to the log file path shown earlier. +- Create a new code cell block using Runme's [CWD feature](/configuration/cell-level#cell-cwd-current-working-directory) and configure the path for that code cell block to the log file path shown earlier. - Run the command `ls -la` to access the file's content, as shown below. ![Check the list](/img/integration/runme-foyle-json-file.png) diff --git a/docs/guide/k8s/helm.md b/docs/guide/k8s/helm.md index 28b3a65e..740a424f 100644 --- a/docs/guide/k8s/helm.md +++ b/docs/guide/k8s/helm.md @@ -112,7 +112,7 @@ Now, you have successfully installed it with your Runme terminal:tada: After installing your Helm packages, you can upgrade them. The `helm upgrade` command upgrades a release to a new version of a chart or applies changes to an existing release. Helm plugins are external tools or extensions that enhance the functionality of the Helm CLI. -With Runme, you can modify the [working directory](/configuration/cell-level#cells-current-working-directory) for your code cell to a file directory of your choice. This enables you to easily run `values.yaml` even if the file is not located in the same directory as your markdown file. +With Runme, you can modify the [working directory](/configuration/cell-level#cell-cwd-current-working-directory) for your code cell to a file directory of your choice. This enables you to easily run `values.yaml` even if the file is not located in the same directory as your markdown file. To upgrade the Ingress package installed earlier, run the command below: diff --git a/docs/guide/k8s/istio.md b/docs/guide/k8s/istio.md index 7b32da3a..1115a0ee 100644 --- a/docs/guide/k8s/istio.md +++ b/docs/guide/k8s/istio.md @@ -139,7 +139,7 @@ kubectl apply -f samples/bookinfo/platform/kube/bookinfo.yaml ![bookinfo](/img/guide-page/runme-bookinfo.png) -Using the [Runme cwd feature](https://docs.runme.dev/configuration/cell-level#cells-current-working-directory), you can confidently set your code cell block to the path where `samples/bookinfo/platform/kube/bookinfo.yaml` is located on your local machine (the sample folder is inside of `istio-` that you downloaded earlier). +Using the [Runme cwd feature](https://docs.runme.dev/configuration/cell-level#cell-cwd-current-working-directory), you can confidently set your code cell block to the path where `samples/bookinfo/platform/kube/bookinfo.yaml` is located on your local machine (the sample folder is inside of `istio-` that you downloaded earlier). ## Expose the Application @@ -151,7 +151,7 @@ kubectl apply -f samples/bookinfo/networking/bookinfo-gateway.yaml ![gateway](/img/guide-page/runme-bookinfo-gateway.png) -[Runme cwd feature](https://docs.runme.dev/configuration/cell-level#cells-current-working-directory) here to set your code cell block to the path where `samples/bookinfo/platform/kube/bookinfo.yaml` is located (the sample folder is inside of `istio-` that you downloaded earlier). +[Runme cwd feature](https://docs.runme.dev/configuration/cell-level#cell-cwd-current-working-directory) here to set your code cell block to the path where `samples/bookinfo/platform/kube/bookinfo.yaml` is located (the sample folder is inside of `istio-` that you downloaded earlier). ## Verify the Application @@ -319,7 +319,7 @@ kubectl apply -f samples/addons ![runme-sample-addons](/img/guide-page/runme-samples-addons.png) -Using the [Runme cwd feature](/configuration/cell-level#cells-current-working-directory), you can confidently set your code cell block to the path where the samples folder is located on your local machine (the sample folder is inside of `istio-` that you downloaded earlier). +Using the [Runme cwd feature](/configuration/cell-level#cell-cwd-current-working-directory), you can confidently set your code cell block to the path where the samples folder is located on your local machine (the sample folder is inside of `istio-` that you downloaded earlier). ## Cleanup diff --git a/docs/guide/k8s/replicaset.md b/docs/guide/k8s/replicaset.md index aae5650c..24e15f00 100644 --- a/docs/guide/k8s/replicaset.md +++ b/docs/guide/k8s/replicaset.md @@ -40,7 +40,7 @@ When this command is successfully executed in Runme, this is the output. With this command, you can create the resources for ReplicaSets based on the definitions provided in the file. -With this command, you can create the resources for ReplicaSets based on the definitions provided in the file. However, if your manifest.yaml file does not exist in the same directory as your Markdown file, you can use [Runme’s cell working directory feature](/configuration/cell-level#cells-current-working-directory) to set its directory. +With this command, you can create the resources for ReplicaSets based on the definitions provided in the file. However, if your manifest.yaml file does not exist in the same directory as your Markdown file, you can use [Runme’s cell working directory feature](/configuration/cell-level#cell-cwd-current-working-directory) to set its directory. **Get Information About ReplicaSets** diff --git a/vercel.json b/vercel.json index 669f1465..a85c9fa5 100644 --- a/vercel.json +++ b/vercel.json @@ -37,7 +37,7 @@ }, { "source": "/r/extension/cwd", - "destination": "https://docs.runme.dev/configuration/cell-level#cells-current-working-directory", + "destination": "https://docs.runme.dev/configuration/cell-level#cell-cwd-current-working-directory", "permanent": false }, {