Skip to content

Commit 2e9de6f

Browse files
committed
only modify my file
1 parent b61e14a commit 2e9de6f

File tree

4 files changed

+15
-20
lines changed

4 files changed

+15
-20
lines changed

docs/docs/community/plugins.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,5 +12,6 @@ You can learn to use and create Nebari extensions in the [extension mechanism do
1212

1313
The following community-developed extensions are recognized and verified by the Nebari development team.
1414

15-
- [nebari-mlflow-aws](https://github.com/MetroStar/nebari-mlflow-aws)
16-
- [nebari-label-studio](https://github.com/MetroStar/nebari-label-studio)
15+
- The **[ML Flow extension for AWS](https://github.com/MetroStar/nebari-mlflow-aws)** is designed to integrate [MLFlow](https://mlflow.org/) into Nebari deployments utilizing AWS (Amazon Web Services) as the provider. It provides a robust, collaborative environment for AI/ML professionals to manage experiments, track metrics, and deploy models.
16+
- The **[Label Studio](https://github.com/MetroStar/nebari-label-studio)** integrates [Label Studio](https://labelstud.io/) into the Nebari platform, allowing seamless labeling functionality within Nebari. Utilizing Python, Terraform, Kubernetes, and Helm charts, the plugin provides a configurable deployment and authentication through Keycloak.
17+
- The **[Self Registration](https://github.com/nebari-dev/nebari-self-registration)** extension allows potential new users of a Nebari deployment to self-register through a coupon code. A new self-registration page is generated on the Nebari server where users can input their information and a coupon code. Once the form is validated, the new user will be auto-generated on the Nebari deployment. It can also be configured to give new users a set expiration date.

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,13 @@ description: Best Practices for Managing Your Python Environment
66

77
# Nebari Deployment Python Environment Setup
88

9+
To configure and deploy the Nebari platform, you'll first need to set up your python environment.
10+
911
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].
1012

1113
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.
1214

13-
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.
15+
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.
1416

1517
```
1618
conda create -n nebari0

docs/docs/how-tos/upgrade-kubernetes-version.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,8 @@ This upgrade process bumps the version of the control plane along with all node
2626
1. Upgrading the kubernetes version of the node groups will cause downtime so please plan accordingly. We also recommend [backing up your data](./manual-backup.md) before starting this upgrade process.
2727
2. Kubernetes versions can only be upgraded one minor version at a time. If you're running on 1.24, and need to upgrade to 1.26, you will first need to upgrade to 1.25.
2828
3. Downgrading to a lower version of Kubernetes is dangerous and we strongly advise against it!
29-
:::
29+
30+
:::
3031

3132
<Tabs>
3233

docs/docs/tutorials/create-dashboard.md

Lines changed: 7 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -127,22 +127,13 @@ Feel free to add more plots or different styles to your plots!
127127

128128
## Deploy the dashboard
129129

130-
1. In the Nebari Home Page (in the top navigation, `Nebari` -> `Hub Control Panel`) click on **"Create App"** to create a new web application for your dashboard.
131-
2. In the app creation interface, enter or select the following:
132-
133-
- **Display Name** - Provide meaningful name for your application
134-
- **Description (optional)** - Add addition information about the application
135-
- **Thumbnail (optional)** - Choose a meaningful thumbnail for your application. The default thumbnail is the application framework's logo.
136-
- **Framework** - Select the framework used by your application. For this tutorial, select Panel.
137-
- **Filepath** - Path (from root in JupyterLab) to your application code file. For this tutorial, path to the Jupyter Notebook.
138-
- **Conda Environment** - Same [environment](#1-create-environment-and-notebook) used while developing your notebook/script which has `jhub-apps` and the corresponding framework.
139-
- **Spawner profile** - Instance type (i.e. machines with CPU/RAM/GPU resources) required for running your application.
140-
- **Allow Public Access** - Toggle to share the application with your team.
141-
142-
3. 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.
143-
4. 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.
144-
5. 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).
145-
6. JHub App Launcher will deploy your app (which can take several minutes to complete) and automatically redirect you to it.
130+
<Tabs>
131+
<TabItem value="jhub-apps" label="JHub App Launcher" default>
132+
133+
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.
134+
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.
135+
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).
136+
4. JHub App Launcher will deploy your app (which can take several minutes to complete) and automatically redirect you to it.
146137

147138
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.
148139

0 commit comments

Comments
 (0)