From 2482de106beb903806d790fb6a429177120b252b Mon Sep 17 00:00:00 2001 From: Pavithra Eswaramoorthy Date: Mon, 14 Nov 2022 19:23:02 +0530 Subject: [PATCH] tag images to add/update alt-text --- docs/docs/get-started/cloud-providers.mdx | 8 ++++---- docs/docs/get-started/installing-nebari.md | 4 ++-- docs/docs/how-tos/configure-keycloak-howto.md | 20 +++++++++---------- docs/docs/how-tos/debug-nebari.mdx | 2 +- docs/docs/how-tos/domain-registry.md | 10 +++++----- .../docs/how-tos/login-thru-keycloak-howto.md | 12 +++++------ docs/docs/how-tos/nebari-aws.md | 6 +++--- docs/docs/how-tos/nebari-azure.md | 6 +++--- docs/docs/how-tos/nebari-destroy.md | 6 +++--- docs/docs/how-tos/nebari-do.md | 6 +++--- docs/docs/how-tos/nebari-gcp.md | 6 +++--- docs/docs/how-tos/using-vscode.md | 16 +++++++-------- docs/docs/troubleshooting.mdx | 2 +- docs/docs/tutorials/creating-cds-dashboard.md | 2 +- docs/docs/tutorials/using_dask.md | 10 +++++----- 15 files changed, 58 insertions(+), 58 deletions(-) diff --git a/docs/docs/get-started/cloud-providers.mdx b/docs/docs/get-started/cloud-providers.mdx index 28dd9d01..feb9e1fb 100644 --- a/docs/docs/get-started/cloud-providers.mdx +++ b/docs/docs/get-started/cloud-providers.mdx @@ -28,7 +28,7 @@ import TabItem from '@theme/TabItem';
- +
[Google GCP](https://cloud.google.com/) (also known as Google Cloud Platform or GCP) is a provider of computing resources for developing, deploying, and operating computing services. @@ -39,7 +39,7 @@ For detailed instructions on how to deploy Nebari on **GCP** visit the [How to d
- +
[DigitalOcean](https://docs.digitalocean.com/products/kubernetes/) is a cloud hosting provider that offers cloud computing services and Infrastructure as a Service (IaaS) known for its pricing and scalability. @@ -50,7 +50,7 @@ For detailed instructions on how to deploy Nebari on **Digital Ocean** visit the
- +
[Amazon Web Services (AWS)](https://aws.amazon.com/eks/) is a comprehensive, evolving cloud computing platform provided by Amazon that includes a mixture of infrastructure as a service (IaaS), platform as a service (PaaS) and packaged software as a service (SaaS) offerings. @@ -61,7 +61,7 @@ For detailed instructions on how to deploy Nebari on **AWS** visit the [How to d
- +
[Microsoft Azure](https://azure.microsoft.com/en-us/services/kubernetes-service/) is Microsoft's public cloud computing platform. It provides a range of cloud services, including compute, analytics, storage and networking. diff --git a/docs/docs/get-started/installing-nebari.md b/docs/docs/get-started/installing-nebari.md index 86d1e5b9..7133e109 100644 --- a/docs/docs/get-started/installing-nebari.md +++ b/docs/docs/get-started/installing-nebari.md @@ -55,7 +55,7 @@ You can verify that Nebari is properly installed, and you are able to execute th nebari --help ``` -![A representation of the output generated when Nebari help command argument is executed, the output contains a list of the available commands and their use.](/img/get-started/nebari-help.png "Nebari's help command line output") +![A representation of the output generated when Nebari help command argument is executed, the output contains a list of the available commands and their use. ](/img/get-started/nebari-help.png "Nebari's help command line output") :::note Troubleshooting If you are unable to successfully validate the Nebari installation above, you may want to check out our [troubleshooting guide][nebari-troubleshooting]. @@ -75,7 +75,7 @@ You can pass the `--help` flag to the `init` command to check all the arguments nebari init --help ``` -![A representation of the output generated when Nebari init help command is executed, the output contains a list of the available options and arguments and their use.](/img/get-started/nebari-init-help-2.png "Nebari's init help command line output") +![A representation of the output generated when Nebari init help command is executed, the output contains a list of the available options and arguments and their use. ](/img/get-started/nebari-init-help-2.png "Nebari's init help command line output") :::tip You can pass the `--guided-init` flag to the `init` command to interact with Guided Init Wizard. diff --git a/docs/docs/how-tos/configure-keycloak-howto.md b/docs/docs/how-tos/configure-keycloak-howto.md index e629c36a..82660d03 100644 --- a/docs/docs/how-tos/configure-keycloak-howto.md +++ b/docs/docs/how-tos/configure-keycloak-howto.md @@ -40,20 +40,20 @@ After the initial deployment, it is **highly** recommended that you change the K 1. To change the `root` user password, go to your Nebari instance's admin dashboard - e.g., something like `https://{your-nebari-domain}/auth/admin/` and log in with the root password provided.

- Nebari admin view - Root Login to Keycloak form + Nebari admin view - Root Login to Keycloak form

2. From there, click on the **Root** dropdown in the top right of the screen, and select **Manage account**. - ![Keycloak root user page - manage account tab selected](/img/how-tos/keycloak_root_user_manage_account.png) + ![Keycloak root user page - manage account tab selected ](/img/how-tos/keycloak_root_user_manage_account.png) 3. Under **Account Security** click **Signing In**. - ![Keycloak root user page - account security](/img/how-tos/keycloak_root_user_account_security.png) + ![Keycloak root user page - account security ](/img/how-tos/keycloak_root_user_account_security.png) 4. In the Password section, click the **Update** button. This will guide you through entering your existing root password, and then creating a new password. - ![Keycloak root user page - account security, update password](/img/how-tos/keycloak_root_user_update_password.png) + ![Keycloak root user page - account security, update password ](/img/how-tos/keycloak_root_user_update_password.png) :::warning The `security.keycloak.initial_root_password` field in `nebari-config.yaml` has no effect after changing the `root` password. If you redeploy Nebari it **will not reset** the password back to the old one (or anything else that might be in the field in your YAML file). We strongly recommend you delete this field to prevent later confusion. @@ -83,7 +83,7 @@ Steps to create a new user: 2. Click the **Add user** button, and you will see the new user form: - ![Keycloak add user tab screenshot - new user form](/img/how-tos/keycloak_add_users.png) + ![Keycloak add user tab screenshot - new user form ](/img/how-tos/keycloak_add_users.png) 3. Fill out the three fields outlined above. These are **Username**, **Email**, and **Groups**. (See explanation below). Then click **save**. @@ -110,7 +110,7 @@ If you are using the password authentication provider, you will also need to def If using Auth0, GitHub or any other identity provider, the password field is not required. ::: -![Keycloak add user > credentials tab screenshot - set password](/img/how-tos/keycloak_user_password.png) +![Keycloak add user > credentials tab screenshot - set password ](/img/how-tos/keycloak_user_password.png) ### Add user from the command line @@ -130,7 +130,7 @@ This will create a new user `` under the `analyst` group, with the ini Your new user can now log in to Nebari, visit your provided Nebari domain URI which will take you to the login form page and follow the [How-to login in to Nebari and start a server][keycloak-login]. -![Nebari - Log in to Keycloak page](/img/how-tos/nebari_login_screen.png) +![Nebari - Log in to Keycloak page ](/img/how-tos/nebari_login_screen.png) ## In-depth look at Roles and Groups @@ -162,15 +162,15 @@ As an example, we create a new group named `conda-store-manager`. This group wil 1. Click **New** in the upper-right hand corner under **Groups**. -![Keycloak groups tab screenshot - user groups view](/img/how-tos/keycloak_groups.png) +![Keycloak groups tab screenshot - user groups view] (/img/how-tos/keycloak_groups.png) - Then, give the new group an appropriate name. -![Keycloak add group form - name field set to conda-store-manager](/img/how-tos/keycloak_new_group1.png) +![Keycloak add group form - name field set to conda-store-manager ](/img/how-tos/keycloak_new_group1.png) 2. Under **Role Mapping**, add the appropriate **Client Roles** as needed; there should be no need to update the **Realm Roles**. -![Keycloak group conda-store-manager form - role mappings tab focused with expanded client roles dropdown](/img/how-tos/keycloak_new_group2.png) +![Keycloak group conda-store-manager form - role mappings tab focused with expanded client roles dropdown ](/img/how-tos/keycloak_new_group2.png) In this example, the new group only has one mapped role, `conda_store_admin`; however, it's possible to attach multiple **Client Roles** to a single group. diff --git a/docs/docs/how-tos/debug-nebari.mdx b/docs/docs/how-tos/debug-nebari.mdx index 9df20099..2b3acbfd 100644 --- a/docs/docs/how-tos/debug-nebari.mdx +++ b/docs/docs/how-tos/debug-nebari.mdx @@ -100,7 +100,7 @@ configuration in the `kubeconfig` to dial the connection with the cluster. To view all the current processes press 0: -![Image of the k9s terminal UI](/img/how-tos/k9s_UI.png) +![Image of the k9s terminal UI ](/img/how-tos/k9s_UI.png) Using `k9s` you can inspect any services launched by your cluster. For example, if your cluster has problems with the network traffic tunnel diff --git a/docs/docs/how-tos/domain-registry.md b/docs/docs/how-tos/domain-registry.md index 121d3377..aaf93bb8 100644 --- a/docs/docs/how-tos/domain-registry.md +++ b/docs/docs/how-tos/domain-registry.md @@ -36,15 +36,15 @@ To generate a token follow the steps below. For additional information, see the - Under Profile, select the API Tokens menu and click on Create API Token. -- On Edit zone DNS click on Use Template.![screenshot Cloudflare edit Zone DNS](/img/how-tos/cloudflare_auth_1.png). +- On Edit zone DNS click on Use Template.![screenshot Cloudflare edit Zone DNS ](/img/how-tos/cloudflare_auth_1.png). -- Configure Permissions such as the image below:![screenshot Cloudflare Permissions edit](/img/how-tos/cloudflare_permissions_2.1.1.png) +- Configure Permissions such as the image below:![screenshot Cloudflare Permissions edit ](/img/how-tos/cloudflare_permissions_2.1.1.png) -- On Account Resources set the configuration to include your desired account.![screenshot Cloudflare account resources](/img/how-tos/cloudflare_account_resources_scr.png) +- On Account Resources set the configuration to include your desired account.![screenshot Cloudflare account resources ](/img/how-tos/cloudflare_account_resources_scr.png) -- On Zone Resources set it to Include | Specific zone and your domain name.![screenshot Cloudflare zone resources](/img/how-tos/cloudflare_zone_resources.png) +- On Zone Resources set it to Include | Specific zone and your domain name.![screenshot Cloudflare zone resources ](/img/how-tos/cloudflare_zone_resources.png) -- Click continue to summary.![screenshot Cloudflare summary](/img/how-tos/cloudflare_summary.png) +- Click continue to summary.![screenshot Cloudflare summary ](/img/how-tos/cloudflare_summary.png) - Click on the Create Token button and set the token generated as an environment variable on your machine. diff --git a/docs/docs/how-tos/login-thru-keycloak-howto.md b/docs/docs/how-tos/login-thru-keycloak-howto.md index 54aa4722..f5beaaac 100644 --- a/docs/docs/how-tos/login-thru-keycloak-howto.md +++ b/docs/docs/how-tos/login-thru-keycloak-howto.md @@ -16,7 +16,7 @@ Navigate to the cluster homepage, for instance [`https://demo.nebari.dev`](https Once on the site, you will be prompted to log in, similar to the login page shown in the image below. -![Nebari login screen](/img/how-tos/nebari_login_screen.png) +![Nebari login screen ](/img/how-tos/nebari_login_screen.png) Nebari uses [Keycloak](https://www.keycloak.org/), an open-source identity and access management tool. Keycloak is a centralized location for administrators to add new users, create user groups and update roles. For more information, see the [How to Configure Keycloak][nebari-keycloak] docs. @@ -33,12 +33,12 @@ For more information on how to configure Keycloak, and add new users, review the In this example, Auth0 is acting as our identity provider. To continue the login process, the user selects the `Auth0` button and logs into through Auth0.

-Nebari Keycloak auth screen - shows a form to provide username or password or to authenticate through Auth0 +Nebari Keycloak auth screen - shows a form to provide username or password or to authenticate through Auth0

Once authenticated, you will be forwarded to the main JupyterHub page. On this page, you will find links to all of Nebari's core features, and it is where you can launch your JupyterLab pod. If you are an admin, you'll also have access to the JupyterHub `Admin` management. -![Nebari dashboard main screen - displays a button "Start my server"](/img/how-tos/nebari_main_hub_page.png) +![Nebari dashboard main screen - displays a button "Start my server" ](/img/how-tos/nebari_main_hub_page.png) ## 3. Selecting a Profile @@ -49,7 +49,7 @@ The customized profiles will give you access to fixed cloud resources. In this e These options are configured by your administrator. A more detailed explanation of dedicated profiles can be found in the Profiles section of the advanced configuration page. -![Nebari select profile](/img/how-tos/nebari_select_profile.png) +![Nebari select profile ](/img/how-tos/nebari_select_profile.png) ## 4. Starting your server @@ -57,14 +57,14 @@ Once an appropriate profile has been selected, click `start`. At this point, you Ultimately this autoscaling feature helps reduce costs when the cluster is idle. A successful launch should look similar to the image below. -![Nebari start server](/img/how-tos/nebari_server_start.png) +![Nebari start server ](/img/how-tos/nebari_server_start.png)
Event Log During this time you might see some log messages that detail the autoscaling process. To view all the logs, click the **Event Log** button. They should look similar to the following: -![Nebari event log](/img/how-tos/keycloak_start_event_logs.png) +![Nebari event log ](/img/how-tos/keycloak_start_event_logs.png)
diff --git a/docs/docs/how-tos/nebari-aws.md b/docs/docs/how-tos/nebari-aws.md index fd966688..58499734 100644 --- a/docs/docs/how-tos/nebari-aws.md +++ b/docs/docs/how-tos/nebari-aws.md @@ -115,7 +115,7 @@ environment variables have been properly set. It is time to initialize and deplo nebari init --guided-init ``` - ![A representation of the output generated when Nebari init guided-init command is executed.](/img/how-tos/nebari-aws.png) + ![A representation of the output generated when Nebari init guided-init command is executed. ](/img/how-tos/nebari-aws.png) :::tip If you prefer not using the `guided-init` command then you can directly run the `init` command. @@ -181,7 +181,7 @@ To see all the options available for the deploy command, run the following comma nebari deploy --help ``` -![A representation of the output generated when nebari deploy help command is executed.](/img/how-tos/nebari-deploy-help.png) +![A representation of the output generated when nebari deploy help command is executed. ](/img/how-tos/nebari-deploy-help.png) With the `nebari-config.yaml` configuration file now created, Nebari can be deployed for the first time. Type the following command on your command line: @@ -225,7 +225,7 @@ To see all the options available for the destroy command, type the following com nebari destroy --help ``` -![A representation of the output generated when nebari deploy help command is executed.](/img/how-tos/nebari-destroy-help.png) +![A representation of the output generated when nebari deploy help command is executed. ](/img/how-tos/nebari-destroy-help.png) Nebari also has a `destroy` command that works the same way the deploy works but instead of creating the provisioned resources it destroys it. diff --git a/docs/docs/how-tos/nebari-azure.md b/docs/docs/how-tos/nebari-azure.md index 7d4aa898..66d6914f 100644 --- a/docs/docs/how-tos/nebari-azure.md +++ b/docs/docs/how-tos/nebari-azure.md @@ -97,7 +97,7 @@ environment variables have been properly set. It is time to initialize and deplo nebari init --guided-init ``` -![A representation of the output generated when Nebari init guided-init command is executed.](/img/how-tos/nebari-azure.png) +![A representation of the output generated when Nebari init guided-init command is executed. ](/img/how-tos/nebari-azure.png) :::tip If you prefer not using the `guided-init` command then you can directly run the `init` command. @@ -163,7 +163,7 @@ To see all the options available for the deploy command, run the following comma nebari deploy --help ``` -![A representation of the output generated when nebari deploy help command is executed.](/img/how-tos/nebari-deploy-help.png) +![A representation of the output generated when nebari deploy help command is executed. ](/img/how-tos/nebari-deploy-help.png) With the `nebari-config.yaml` configuration file now created, Nebari can be deployed for the first time. Type the following command on your command line: @@ -207,7 +207,7 @@ To see all the options available for the destroy command, type the following com nebari destroy --help ``` -![A representation of the output generated when nebari deploy help command is executed.](/img/how-tos/nebari-destroy-help.png) +![A representation of the output generated when nebari deploy help command is executed. ](/img/how-tos/nebari-destroy-help.png) Nebari also has a `destroy` command that works the same way the deploy works but instead of creating the provisioned resources it destroys it. diff --git a/docs/docs/how-tos/nebari-destroy.md b/docs/docs/how-tos/nebari-destroy.md index b29a98b8..e398290a 100644 --- a/docs/docs/how-tos/nebari-destroy.md +++ b/docs/docs/how-tos/nebari-destroy.md @@ -82,11 +82,11 @@ Here, we outline how to find and destroy resources from the AWS console. 1. Sign in to your AWS account and in the search bar type `Tag Editor` -Search for Tag Editor in the AWS console +Search for Tag Editor in the AWS console 2. From the `Resource Groups & Tag Editor` page, navigate to `Tag Editor` from the left most panel -Navigate to the Tag Editor in the AWS console +Navigate to the Tag Editor in the AWS console 3. Fill out the form as follows: - `Regions` - the region you deployed your Nebari cluster (or select `all regions`) @@ -95,7 +95,7 @@ Here, we outline how to find and destroy resources from the AWS console. - select `Environment` for key (on the left) - enter the namespace you chose for your Nebari cluster (on the right) -Use the Tag Editor to filter for lingering Nebari resources +Use the Tag Editor to filter for lingering Nebari resources 4. From here you can filter further if needed by entering the name of your Nebari cluster. diff --git a/docs/docs/how-tos/nebari-do.md b/docs/docs/how-tos/nebari-do.md index 029103b6..0b3c1859 100644 --- a/docs/docs/how-tos/nebari-do.md +++ b/docs/docs/how-tos/nebari-do.md @@ -95,7 +95,7 @@ environment variables have been properly set. It is time to initialize and deplo nebari init --guided-init ``` -![A representation of the output generated when Nebari init guided-init command is executed.](/img/how-tos/nebari-do.png) +![A representation of the output generated when Nebari init guided-init command is executed. ](/img/how-tos/nebari-do.png) :::tip If you prefer not using the `guided-init` command then you can directly run the `init` command. @@ -161,7 +161,7 @@ To see all the options available for the deploy command, run the following comma nebari deploy --help ``` -![A representation of the output generated when nebari deploy help command is executed.](/img/how-tos/nebari-deploy-help.png) +![A representation of the output generated when nebari deploy help command is executed. ](/img/how-tos/nebari-deploy-help.png) With the `nebari-config.yaml` configuration file now created, Nebari can be deployed for the first time. Type the following command on your command line: @@ -203,7 +203,7 @@ To see all the options available for the destroy command, type the following com nebari destroy --help ``` -![A representation of the output generated when nebari deploy help command is executed.](/img/how-tos/nebari-destroy-help.png) +![A representation of the output generated when nebari deploy help command is executed. ](/img/how-tos/nebari-destroy-help.png) Nebari also has a `destroy` command that works the same way the deploy works but instead of creating the provisioned resources it destroys it. diff --git a/docs/docs/how-tos/nebari-gcp.md b/docs/docs/how-tos/nebari-gcp.md index 23420f20..98f1caca 100644 --- a/docs/docs/how-tos/nebari-gcp.md +++ b/docs/docs/how-tos/nebari-gcp.md @@ -135,7 +135,7 @@ environment variables have been properly set. It is time to initialize and deplo nebari init --guided-init ``` -![A representation of the output generated when Nebari init guided-init command is executed.](/img/how-tos/nebari-gcp.png) +![A representation of the output generated when Nebari init guided-init command is executed. ](/img/how-tos/nebari-gcp.png) :::tip If you prefer not using the `guided-init` command then you can directly run the `init` command. @@ -201,7 +201,7 @@ To see all the options available for the deploy command, run the following comma nebari deploy --help ``` -![A representation of the output generated when nebari deploy help command is executed.](/img/how-tos/nebari-deploy-help.png) +![A representation of the output generated when nebari deploy help command is executed. ](/img/how-tos/nebari-deploy-help.png) With the `nebari-config.yaml` configuration file now created, Nebari can be deployed for the first time. Type the following command on your command line: @@ -245,7 +245,7 @@ To see all the options available for the destroy command, type the following com nebari destroy --help ``` -![A representation of the output generated when nebari deploy help command is executed.](/img/how-tos/nebari-destroy-help.png) +![A representation of the output generated when nebari deploy help command is executed. ](/img/how-tos/nebari-destroy-help.png) Nebari also has a `destroy` command that works the same way the deployment works but instead of creating the provisioned resources it destroys it. diff --git a/docs/docs/how-tos/using-vscode.md b/docs/docs/how-tos/using-vscode.md index 6fdb6501..204fd0af 100644 --- a/docs/docs/how-tos/using-vscode.md +++ b/docs/docs/how-tos/using-vscode.md @@ -15,7 +15,7 @@ to Nebari and spin up a JupyterLab instance. Next, bring up the `New Launcher` window by clicking the `+` in the top left of the screen. Now click on the VS Code logo on the Launcher window. -![JupyterLab Launcher window with VS Code](/img/tutorials/vscode_launcher.png) +![JupyterLab Launcher window with VS Code ](/img/tutorials/vscode_launcher.png) You will now have been redirected to a new web browser page showing the VS Code platform. If you're starting VS Code for the first time, you'll see a @@ -23,7 +23,7 @@ Welcome Page with some helpful links and tips. Feel free to explore! -![VS Code Welcome screen](/img/tutorials/vscode_welcome.png) +![VS Code Welcome screen ](/img/tutorials/vscode_welcome.png) ## VS Code components @@ -63,7 +63,7 @@ hides these files in its Explorer view. Let's click on a file we all have, `.bashrc`. This file was created by Nebari for us. -![VS Code bashrc file](/img/tutorials/vscode_bashrc.png) +![VS Code bashrc file ](/img/tutorials/vscode_bashrc.png) We now have an `Editor` window in which we can modify the file. The default VS Code preferences include an auto-save feature which will continually save @@ -77,7 +77,7 @@ installed by you, and a list of "Popular" extensions you may want to try. Through this interface we can also search the Marketplace for a particular extension. -![VS Code extensions list](/img/tutorials/vscode_extensions_list.png) +![VS Code extensions list ](/img/tutorials/vscode_extensions_list.png) The Python extension is at the top of the list in our example (rightly so!), but if you don't see it here, you can search for it. @@ -102,7 +102,7 @@ some automatic linting tasks through Preferences if you'd like. Add some sample code to your file: -![VS Code new file contents](/img/tutorials/vscode_new_file_contents.png) +![VS Code new file contents ](/img/tutorials/vscode_new_file_contents.png) We also see the VS Code `Terminal` in the previous image. This can be opened with `File -> Terminal -> New Terminal`. @@ -110,16 +110,16 @@ opened with `File -> Terminal -> New Terminal`. Before we run our file, we need to select what Conda environment it should run inside. -![VS Code select conda env](/img/tutorials/vscode_select_env.png) +![VS Code select conda env ](/img/tutorials/vscode_select_env.png) Now we can run our code through the VS Code UI by selecting either `Run Python File` or `Debug Python File` in the top right. -![VS Code run or debug env](/img/tutorials/vscode_run_debug_buttons.png) +![VS Code run or debug env ](/img/tutorials/vscode_run_debug_buttons.png) We can see output in the terminal: -![VS Code view output](/img/tutorials/vscode_output.png) +![VS Code view output ](/img/tutorials/vscode_output.png) As another alternative, we could run code directly from the terminal as well. diff --git a/docs/docs/troubleshooting.mdx b/docs/docs/troubleshooting.mdx index cbec1a01..2d40f319 100644 --- a/docs/docs/troubleshooting.mdx +++ b/docs/docs/troubleshooting.mdx @@ -26,7 +26,7 @@ This is a manual process that consists in copying over the yaml specifications f Once all environments are migrated, you will be able to delete the `default` and `filesystem` namespaces using the `delete` option from the conda-store UI: -![delete-namespace](/img/troubleshooting/delete_namespace.png) +![delete-namespace ](/img/troubleshooting/delete_namespace.png) :::warning Both the `filesystem` and `nebari-git` are built-in namespaces that are used by Nebari. diff --git a/docs/docs/tutorials/creating-cds-dashboard.md b/docs/docs/tutorials/creating-cds-dashboard.md index a48a6980..1a433f79 100644 --- a/docs/docs/tutorials/creating-cds-dashboard.md +++ b/docs/docs/tutorials/creating-cds-dashboard.md @@ -74,7 +74,7 @@ In this section, you'll use CDS Dashboards to publish and share your newly creat To begin, click on the top left tab navigate to `File` -> `Hub Control Panel` -> `Dashboards`. Click on the button `New Dashboard`. You will now be presented with a new window where you'll need to provide additional details for your dashboard (see image below for reference). -![CDS dashboard configuration screenshot](/img/tutorials/window_dashboard_configuration_example.png) +![CDS dashboard configuration screenshot ](/img/tutorials/window_dashboard_configuration_example.png) 1. Give your dashboard a name, for example, `Trees`. This name will be the name of your shareable dashboard, so make sure to give this a meaningful name. 2. Add a short description, for example, `Insights and more`. diff --git a/docs/docs/tutorials/using_dask.md b/docs/docs/tutorials/using_dask.md index 4b04bda4..e5f9e8a0 100644 --- a/docs/docs/tutorials/using_dask.md +++ b/docs/docs/tutorials/using_dask.md @@ -57,7 +57,7 @@ options = gateway.cluster_options() options ``` -![Nebari - Cluster Options UI](/img/tutorials/cluster_options.png) +![Nebari - Cluster Options UI ](/img/tutorials/cluster_options.png) Using the `Cluster Options` interface, you can specify the `conda` environment, the instance type, and any additional environment variables you'll need. @@ -80,7 +80,7 @@ The Dask worker environment is specified in your deployment directory under `/im ``` Once you run the cell, you'll see the following: - ![Creating a Gateway Cluster UI](/img/tutorials/cluster_creation.png) + ![Creating a Gateway Cluster UI ](/img/tutorials/cluster_creation.png) 2. You have the option to choose between `Manual Scaling` and `Adaptive Scaling`. @@ -106,7 +106,7 @@ client ``` On executing the cell, you'll see the following: -![Nebari - Dask client UI showing details of the newly created Dask cluster](/img/tutorials/dask_client.png) +![Nebari - Dask client UI showing details of the newly created Dask cluster ](/img/tutorials/dask_client.png) The `Dask Client` interface gives us a brief summary of everything we've set up so far. @@ -216,7 +216,7 @@ and the small rectangles within are the individual tasks. Check out the [Dask Documentation](https://docs.dask.org/en/stable/dashboard.html) for more information. -![Dask diagnostic UI - showing four parallel computation streams](/img/tutorials/dask_diagostic_UI.png) +![Dask diagnostic UI - showing four parallel computation streams ](/img/tutorials/dask_diagostic_UI.png) ### Shutting down the cluster @@ -240,7 +240,7 @@ The [Dask-labextension](https://github.com/dask/dask-labextension) provides a Ju as well as embed Dask's dashboard plots directly into JupyterLab panes. Nebari includes this extension by default, elevating the overall developer experience. -![Dask-labextension UI In JupyterLab - displays the demo notebook and a list of cluster settings](/img/tutorials/dask_labextension.png) +![Dask-labextension UI In JupyterLab - displays the demo notebook and a list of cluster settings ](/img/tutorials/dask_labextension.png) ## Step 6 - Using Dask safely