Merge pull request #508 from nebari-dev/fix_yarn_lint

Fix yarn lint/format

Author: viniciusdc

.github/workflows/test-website.yml

@@ -33,5 +33,8 @@ jobs:
       - name: Lint 🔍
         run: yarn run lint
 
+      - name: Format 🥇
+        run: yarn run format
+
       - name: Build site 🔨
         run: yarn run build

docs/docs/explanations/advanced-custom-settings.md

@@ -277,6 +277,7 @@ Select the virtual network and subnet name under the networking settings of your
 and then follow the usual deployment instructions as you would deploy from your local machine.
 
 =======
+
 #### Conda store worker
 
 You can use the following settings to change the defaults settings (shown) used for Conda store workers.

docs/docs/how-tos/access-logs-loki.md

@@ -14,7 +14,7 @@ To view the Loki logs via Grafana in Nebari, you'll need to have [set up monitor
 Access the Monitoring UI for your Nebari installation at https://{your-nebari-domain}/monitoring/.
 
 :::note
-The **Explore** functionality shown below is only available to users who have `grafana_admin` permissions.  In Nebari's default configuration, only the users in the `admin` Keycloak user group will have this role.  `grafana_admin` is a client role in Keycloak which can be assigned to other groups or users.  See [Configure Keycloak](/docs/how-tos/configuring-keycloak#in-depth-look-at-roles-and-groups) for more information.
+The **Explore** functionality shown below is only available to users who have `grafana_admin` permissions. In Nebari's default configuration, only the users in the `admin` Keycloak user group will have this role. `grafana_admin` is a client role in Keycloak which can be assigned to other groups or users. See [Configure Keycloak](/docs/how-tos/configuring-keycloak#in-depth-look-at-roles-and-groups) for more information.
 :::
 
 First, click "Explore".

docs/docs/how-tos/jhub-app-launcher.md

@@ -8,8 +8,8 @@ description: Using JHub App Launcher with Nebari
 
 [JHub App Launcher](https://jhub-apps.nebari.dev/) is a generalized server launcher
 for deploying web applications via JupyterHub. The App Launcher serves as the "home"
-page for Nebari - providing access to various Nebari services (e.g. JupyterLab, VS Code, 
-conda-store) and access to deploy custom web apps. 
+page for Nebari - providing access to various Nebari services (e.g. JupyterLab, VS Code,
+conda-store) and access to deploy custom web apps.
 
 ![JHub App Launcher home screen](/img/how-tos/jhub_apps_home.png)
 
@@ -42,11 +42,11 @@ and is not enabled by default.
 
 ## Usage
 
-Documentation on how to create apps is included in the 
+Documentation on how to create apps is included in the
 [JHub Apps documentation](https://jhub-apps.nebari.dev/docs/category/create-apps).
-Deployed apps on Nebari will utilize environments from conda-store. All apps 
-will need to include `jhsingle-native-proxy >= 0.8.2` in their environment along with 
-other framework-specific dependencies. For example, deploying a `panel` app will 
-require `panel` itself and additional tools for deploying `panel` apps such as 
-`bokeh-root-cmd >= 0.1.2`. See the documentation for specific requirements on 
-each framework. 
+Deployed apps on Nebari will utilize environments from conda-store. All apps
+will need to include `jhsingle-native-proxy >= 0.8.2` in their environment along with
+other framework-specific dependencies. For example, deploying a `panel` app will
+require `panel` itself and additional tools for deploying `panel` apps such as
+`bokeh-root-cmd >= 0.1.2`. See the documentation for specific requirements on
+each framework.

docs/docs/how-tos/nebari-environment-management.md

@@ -6,13 +6,13 @@ description: Best Practices for Managing Your Python Environment
 
 # Nebari Deployment Python Environment Setup
 
-To configure and deploy the Nebari platform, you'll first need to set up your python environment. 
+To configure and deploy the Nebari platform, you'll first need to set up your python environment.
 
 Nebari configuration and deployment is highly dependent on the version of the Nebari CLI that you have active when you run `nebari` commands. A such, we highly recommend [installing Conda](https://docs.anaconda.com/free/anaconda/install/) for managing isolated Python environments, especially when working on more than one Nebari deployment from the same machine or using [Nebari extensions][nebari-extension-system].
 
 Once installed, you can use [manage environments](https://conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#managing-environments) in different ways.
 
-This is a simple way to set up a new Conda environment named `nebari0` with a specific Nebari version and exactly one extension installed. This `nebari0` environment will store all of our packages, including those installed with `pip` because when **pip** is installed into an active conda environment, packages which are then installed with pip will not be saved in the global namespace_. This especially critical when working with extensions, because `nebari` will detect and apply any extensions installed in your Python environment when it runs.
+This is a simple way to set up a new Conda environment named `nebari0` with a specific Nebari version and exactly one extension installed. This `nebari0` environment will store all of our packages, including those installed with `pip` because when **pip** is installed into an active conda environment, packages which are then installed with pip will not be saved in the global namespace. This especially critical when working with extensions, because `nebari` will detect and apply any extensions installed in your Python environment when it runs.
 
 ```
 conda create -n nebari0

docs/docs/references/RELEASE.md

@@ -14,34 +14,34 @@ This file is copied to nebari-dev/nebari-docs using a GitHub Action. -->
 > NOTE: Support for Digital Ocean deployments using CLI commands and related Terraform modules is being deprecated. Although Digital Ocean will no longer be directly supported in future releases, you can still deploy to Digital Ocean infrastructure using the current `existing` deployment option.
 
 ## What's Changed
-* Enable authentication by default in jupyter-server by @krassowski in https://github.com/nebari-dev/nebari/pull/2288
-* remove dns sleep by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2550
-* Conda-store permissions v2 + load roles from keycloak by @aktech in https://github.com/nebari-dev/nebari/pull/2531
-* Restrict public access and add bucket encryption using cmk by @dcmcand in https://github.com/nebari-dev/nebari/pull/2525
-* Add overwrite to AWS coredns addon by @dcmcand in https://github.com/nebari-dev/nebari/pull/2538
-* Add a default roles at initialisation by @aktech in https://github.com/nebari-dev/nebari/pull/2546
-* Hide gallery section if no exhibits are configured by @krassowski in https://github.com/nebari-dev/nebari/pull/2549
-* Add note about ~/.bash_profile by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2575
-* Expose jupyterlab-gallery branch and depth options by @krassowski in https://github.com/nebari-dev/nebari/pull/2556
-* #2566 Upgrade Jupyterhub ssh image by @arjxn-py in https://github.com/nebari-dev/nebari/pull/2576
-* Stop copying unnecessary files into user home directory by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2578
-* Include deprecation notes for init/deploy subcommands by @viniciusdc in https://github.com/nebari-dev/nebari/pull/2582
-* Only download jar if file doesn't exist by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2588
-* Remove unnecessary experimental flag by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2606
-* Add typos spell checker to pre-commit by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2568
-* Enh 2451 skip conditionals by @BrianCashProf in https://github.com/nebari-dev/nebari/pull/2569
-* Improve codespell support: adjust and concentrate config to pyproject.toml and fix more typos by @yarikoptic in https://github.com/nebari-dev/nebari/pull/2583
-* Move codespell config to pyproject.toml only by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2611
-* Add `depends_on` for bucket encryption by @viniciusdc in https://github.com/nebari-dev/nebari/pull/2615
+
+- Enable authentication by default in jupyter-server by @krassowski in https://github.com/nebari-dev/nebari/pull/2288
+- remove dns sleep by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2550
+- Conda-store permissions v2 + load roles from keycloak by @aktech in https://github.com/nebari-dev/nebari/pull/2531
+- Restrict public access and add bucket encryption using cmk by @dcmcand in https://github.com/nebari-dev/nebari/pull/2525
+- Add overwrite to AWS coredns addon by @dcmcand in https://github.com/nebari-dev/nebari/pull/2538
+- Add a default roles at initialisation by @aktech in https://github.com/nebari-dev/nebari/pull/2546
+- Hide gallery section if no exhibits are configured by @krassowski in https://github.com/nebari-dev/nebari/pull/2549
+- Add note about ~/.bash_profile by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2575
+- Expose jupyterlab-gallery branch and depth options by @krassowski in https://github.com/nebari-dev/nebari/pull/2556
+- #2566 Upgrade Jupyterhub ssh image by @arjxn-py in https://github.com/nebari-dev/nebari/pull/2576
+- Stop copying unnecessary files into user home directory by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2578
+- Include deprecation notes for init/deploy subcommands by @viniciusdc in https://github.com/nebari-dev/nebari/pull/2582
+- Only download jar if file doesn't exist by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2588
+- Remove unnecessary experimental flag by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2606
+- Add typos spell checker to pre-commit by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2568
+- Enh 2451 skip conditionals by @BrianCashProf in https://github.com/nebari-dev/nebari/pull/2569
+- Improve codespell support: adjust and concentrate config to pyproject.toml and fix more typos by @yarikoptic in https://github.com/nebari-dev/nebari/pull/2583
+- Move codespell config to pyproject.toml only by @Adam-D-Lewis in https://github.com/nebari-dev/nebari/pull/2611
+- Add `depends_on` for bucket encryption by @viniciusdc in https://github.com/nebari-dev/nebari/pull/2615
 
 ## New Contributors
-* @BrianCashProf made their first contribution in https://github.com/nebari-dev/nebari/pull/2569
-* @yarikoptic made their first contribution in https://github.com/nebari-dev/nebari/pull/2583
 
+- @BrianCashProf made their first contribution in https://github.com/nebari-dev/nebari/pull/2569
+- @yarikoptic made their first contribution in https://github.com/nebari-dev/nebari/pull/2583
 
 **Full Changelog**: https://github.com/nebari-dev/nebari/compare/2024.6.1...2024.7.1
 
-
 ### Release 2024.6.1 - June 26, 2024
 
 > NOTE: This release includes an upgrade to the `kube-prometheus-stack` Helm chart, resulting in a newer version of Grafana. When upgrading your Nebari cluster, you will be prompted to have Nebari update some CRDs and delete a DaemonSet on your behalf. If you prefer, you can also run the commands yourself, which will be shown to you. If you have any custom dashboards, you'll also need to back them up by [exporting them as JSON](https://grafana.com/docs/grafana/latest/dashboards/share-dashboards-panels/#export-a-dashboard-as-json), so you can [import them](https://grafana.com/docs/grafana/latest/dashboards/build-dashboards/import-dashboards/#import-a-dashboard) after upgrading.

docs/docs/references/personas.md

@@ -20,7 +20,6 @@ Each persona is placed in a Nebari user group:
 
 **Admin** represents the people who are in charge of deploying Nebari. They are responsible for maintaining and running the day to day maintenance. This may include cloud account management, conda-store maintenance, kubernetes cluster management and adding/removing end users from the deployment. Our admin is [Taylor](#taylor)
 
-
 ## Personas
 
 ---

docs/docs/tutorials/create-dashboard.md

@@ -132,14 +132,13 @@ Feel free to add more plots or different styles to your plots!
 
 1. On the Nebari Home Page (from JupyterLab, click on the Nebari logo in the top right corner or go to `File` -> `Home`) click on **"Create App"** to create a new web application for your dashboard.
 2. Follow the [general instructions](https://jhub-apps.nebari.dev/docs/create-apps/general-app) from the JHub Apps documentation to fill out the `Create app` form.
-3. Click **Next**. You'll be redirected to the Spawner profile page. This page will allow you to select the server in which you want your app to run. These options will vary based on the setup of your Nebari deployment (which server types are available overall) and the permissions of your user (which server types you personally have access to). 
+3. Click **Next**. You'll be redirected to the Spawner profile page. This page will allow you to select the server in which you want your app to run. These options will vary based on the setup of your Nebari deployment (which server types are available overall) and the permissions of your user (which server types you personally have access to).
 4. JHub App Launcher will deploy your app (which can take several minutes to complete) and automatically redirect you to it.
 
 Your dashboard app will be available in the Nebari Home page, under "My Apps". If you allowed shared access, it will be available under "Shared Apps" for those with whom you have shared the app.
 
 </TabItem>
 
-
 <TabItem value="cds-dashboards" label="CDS Dashboard" default>
 
 In this section, you'll use CDS Dashboards ((Nebari v2023.7.1 or earlier)) to publish and share your newly created `panel` dashboard.