From 9f92cb5d75d2b1943008dbacfc743d72bcafa685 Mon Sep 17 00:00:00 2001 From: Pawel Kosiec Date: Tue, 13 Jan 2026 20:44:39 +0100 Subject: [PATCH 1/2] docs: describe development flow and app management --- docs/docs/_prerequisites.mdx | 4 + docs/docs/app-management.mdx | 163 ++++++++++++++++++ docs/docs/core-concepts/_category_.json | 8 - .../principles.md => core-principles.md} | 2 +- docs/docs/development/_prerequisites_app.mdx | 5 + .../development/ai-assisted-development.mdx | 56 ++++++ docs/docs/development/index.mdx | 23 +++ docs/docs/development/local-development.mdx | 21 +++ docs/docs/development/remote-bridge.mdx | 86 +++++++++ docs/docs/index.md | 48 +++--- docs/src/pages/contributing.md | 2 +- 11 files changed, 384 insertions(+), 34 deletions(-) create mode 100644 docs/docs/_prerequisites.mdx create mode 100644 docs/docs/app-management.mdx delete mode 100644 docs/docs/core-concepts/_category_.json rename docs/docs/{core-concepts/principles.md => core-principles.md} (98%) create mode 100644 docs/docs/development/_prerequisites_app.mdx create mode 100644 docs/docs/development/ai-assisted-development.mdx create mode 100644 docs/docs/development/index.mdx create mode 100644 docs/docs/development/local-development.mdx create mode 100644 docs/docs/development/remote-bridge.mdx diff --git a/docs/docs/_prerequisites.mdx b/docs/docs/_prerequisites.mdx new file mode 100644 index 00000000..88a69d15 --- /dev/null +++ b/docs/docs/_prerequisites.mdx @@ -0,0 +1,4 @@ +## Prerequisites + +- [Node.js](https://nodejs.org) environment +- Databricks CLI: install and configure it according to the [official tutorial](https://docs.databricks.com/aws/en/dev-tools/cli/tutorial). \ No newline at end of file diff --git a/docs/docs/app-management.mdx b/docs/docs/app-management.mdx new file mode 100644 index 00000000..32aa41ae --- /dev/null +++ b/docs/docs/app-management.mdx @@ -0,0 +1,163 @@ +--- +sidebar_position: 3 +--- + +import Prerequisites from './_prerequisites.mdx'; + +# App Management + +Manage your AppKit application throughout its lifecycle using the Databricks CLI. This guide covers deploying, starting, stopping, monitoring, and deleting apps. + + + +## Create App + +See the [Quick start](./index.md#quick-start-options) section to create a new Databricks app with AppKit installed. + +## Configuration + +Before deploying your app, configure it according to your needs. See the [Databricks Apps Configuration](https://docs.databricks.com/aws/en/dev-tools/databricks-apps/configuration) documentation for details on: + +- App configuration file (`app.yaml`) +- Environment variables +- Authorization and permissions +- Networking configuration + +## Deploy App + +Deploy your AppKit application using the automated deployment pipeline: + +```bash +databricks experimental dev app deploy +``` + +This command runs a complete deployment pipeline: +1. Builds the frontend (`npm run build`) +2. Deploys the bundle to the workspace +3. Runs the app + +:::note + +For all available options, run: +```bash +databricks experimental dev app deploy --help +``` +::: + +### Examples + +Deploy to the default target: + +```bash +databricks experimental dev app deploy +``` + +Deploy to a specific target: + +```bash +databricks experimental dev app deploy --target prod +``` + +Deploy with custom variables: + +```bash +databricks experimental dev app deploy --var="warehouse_id=abc123" +``` + +Skip the build step for faster iteration: + +```bash +databricks experimental dev app deploy --skip-build +``` + +Force deploy (override Git branch validation): + +```bash +databricks experimental dev app deploy --force +``` + +## Start App + +To start a stopped app, run: + +```bash +databricks apps start {name} +``` + +## Stop App + +Stop a running app without deleting it: + +```bash +databricks apps stop {name} +``` + +## List all apps + +```bash +databricks apps list +``` + +## Get detailed app information + +```bash +databricks apps get {name} +``` + +## Stream App Logs + +Stream application logs in real-time: + +```bash +databricks apps logs {name} +``` + +By default, this shows the most recent 200 log lines and exits. + +> **Note:** For all available options, run `databricks apps logs --help` + +### Examples + +Show the last 50 log lines: + +```bash +databricks apps logs my-app --tail-lines 50 +``` + +Follow logs with a search filter: + +```bash +databricks apps logs my-app --follow --search ERROR +``` + +Filter logs by source: + +```bash +databricks apps logs my-app --follow --source APP +``` + +Save logs to a file: + +```bash +databricks apps logs my-app --follow --output-file app.log +``` + +Stream logs for 5 minutes: + +```bash +databricks apps logs my-app --follow --timeout 5m +``` + +## Delete App + +Permanently delete an app: + +```bash +databricks apps delete {name} +``` + +**⚠️ Warning:** This action cannot be undone. All app data and configurations will be removed. + +## See also + +For more information about Databricks Apps, including platform architecture, use cases, security, and advanced features, see the [Databricks Apps documentation](https://docs.databricks.com/aws/en/dev-tools/databricks-apps/). diff --git a/docs/docs/core-concepts/_category_.json b/docs/docs/core-concepts/_category_.json deleted file mode 100644 index f34390a5..00000000 --- a/docs/docs/core-concepts/_category_.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "label": "Core Concepts", - "position": 2, - "link": { - "type": "generated-index", - "description": "Learn about the fundamental concepts and principles behind AppKit." - } -} diff --git a/docs/docs/core-concepts/principles.md b/docs/docs/core-principles.md similarity index 98% rename from docs/docs/core-concepts/principles.md rename to docs/docs/core-principles.md index c4e0e877..ab094c38 100644 --- a/docs/docs/core-concepts/principles.md +++ b/docs/docs/core-principles.md @@ -1,4 +1,4 @@ -# Principles +# Core Principles Learn about the fundamental concepts and principles behind AppKit. diff --git a/docs/docs/development/_prerequisites_app.mdx b/docs/docs/development/_prerequisites_app.mdx new file mode 100644 index 00000000..32ec33ea --- /dev/null +++ b/docs/docs/development/_prerequisites_app.mdx @@ -0,0 +1,5 @@ +## Prerequisites + +- [Node.js](https://nodejs.org) environment +- Databricks CLI: install and configure it according to the [official tutorial](https://docs.databricks.com/aws/en/dev-tools/cli/tutorial). +- A new Databricks app with AppKit installed. See [Bootstrap a new Databricks app](../index.md#quick-start-options) for more details. diff --git a/docs/docs/development/ai-assisted-development.mdx b/docs/docs/development/ai-assisted-development.mdx new file mode 100644 index 00000000..20e707ca --- /dev/null +++ b/docs/docs/development/ai-assisted-development.mdx @@ -0,0 +1,56 @@ +--- +sidebar_position: 2 +--- + +import Prerequisites from './_prerequisites_app.mdx'; + +# AI-Assisted Development + + + +AppKit integrates with AI coding assistants through the Model Context Protocol (MCP). + +## Installing MCP Server + +To install the Databricks MCP server for your preferred AI assistant, run: + +```bash +databricks experimental apps-mcp install +``` + +## MCP Capabilities + +The MCP server exposes the following capabilities for AI assistants: + +- **Data exploration**: Query catalogs, schemas, tables, and execute SQL +- **CLI command execution**: Deploy and manage apps, and run other workspace operations +- **Workspace resource discovery**: Inspect and navigate workspace resources + +## Example prompts + +Here are some basic examples you can use to explore your app and workspace: + +1. Creating a new basic app + ``` + Create a new Databricks app that displays a dashboard of the users table in main.default. + ``` +1. Introspecting a table schema + ``` + Show me the schema of the users table in main.default. + ``` +1. Creating a new query + ``` + Create a new query to find users created in the last 7 days. + ``` +1. Deploying an app + ``` + Deploy the app to Databricks with the name "my-app". + ``` + +Possibilities are virtually endless. Ask your AI assistant to help you with your app and workspace. + +## LLM Resources + +AppKit provides specialized guidance files to help AI coding assistants work more effectively with the projects. + +If you're building applications using AppKit packages, reference the **[llms.txt](https://github.com/databricks/appkit/blob/main/llms.txt)** file. diff --git a/docs/docs/development/index.mdx b/docs/docs/development/index.mdx new file mode 100644 index 00000000..20fca75f --- /dev/null +++ b/docs/docs/development/index.mdx @@ -0,0 +1,23 @@ +--- +sidebar_position: 2 +--- + +import Prerequisites from './_prerequisites_app.mdx'; + +# Development + +AppKit provides multiple development workflows to suit different needs: local development with hot reload, AI-assisted development with MCP, and remote tunneling to deployed backends. + + + +## Development flows + +There are multiple supported development flows available with AppKit: + +1. **[Local development](./local-development.mdx)**: Run the development server with hot reload for both UI and backend code. This is the default development flow and is suitable for most use cases. +2. **[AI-assisted development](./ai-assisted-development.mdx)**: Use an AI coding assistant connected via the Databricks MCP server to explore data, run CLI commands, and scaffold your app interactively. +3. **[Remote bridge](./remote-bridge.mdx)**: Create a remote bridge to a deployed backend while keeping your queries and UI local. This is useful for testing against production data or debugging deployed backend code without redeploying your app. + +## See also + +- [App Management](../app-management.mdx): Manage your AppKit application throughout its lifecycle using the Databricks CLI diff --git a/docs/docs/development/local-development.mdx b/docs/docs/development/local-development.mdx new file mode 100644 index 00000000..7d995bb2 --- /dev/null +++ b/docs/docs/development/local-development.mdx @@ -0,0 +1,21 @@ +--- +sidebar_position: 1 +--- + +import Prerequisites from './_prerequisites_app.mdx'; + +# Local Development + + + +Once your app is bootstrapped according to the [Manual quick start](../index.md#manual-quick-start) guide, you can start the development server with hot reload for both UI and backend code. + +In the application root directory, run the following command to start the development server: + +```bash +npm run dev +``` + +This command will start the development server with hot reload for both UI and backend code. Open the displayed URL in your browser to see the app. Modify the code in the `src/` directory to see the changes reflected in the browser. + +To see the other available commands, read the `README.md` file in the application root directory. diff --git a/docs/docs/development/remote-bridge.mdx b/docs/docs/development/remote-bridge.mdx new file mode 100644 index 00000000..f7f086e6 --- /dev/null +++ b/docs/docs/development/remote-bridge.mdx @@ -0,0 +1,86 @@ +--- +sidebar_position: 3 +--- + +import Prerequisites from './_prerequisites_app.mdx'; + +# Remote Bridge + + + +Remote bridge allows you to develop against a deployed backend while keeping your UI and queries local. This is useful for testing against production data or debugging deployed backend code without redeploying your app. + +## When to Use Remote Bridge + +Use remote bridge when: +- Testing against production data +- Debugging deployed backend code +- Developing UI without running backend locally +- Collaborating with team members on the same backend + +## Starting and Stopping the Remote Bridge + +To start the remote bridge, run the following command: + +```bash +databricks apps dev-remote --app-name my-app --client-path ./client +``` + +The command will: + +1. Start a local Vite development server +2. Establish a WebSocket bridge to your deployed app +3. Provide two URLs: + + - **App URL**: Direct link for your own use (`?dev=true`) + - **Shareable URL**: Link with tunnel ID for sharing with team members (`?dev=`) + + +:::note + +For all available options, run: +```bash +databricks apps dev-remote --help +``` +::: + +To stop the remote bridge, press `Ctrl+C` in the terminal. + +## Connection Approval + +When you start remote bridge, every time you open the URL in your browser from a new device, you'll be prompted to approve the connection. + +You can provide the URL to your team members to allow them to see the app in their browser. You will still need to approve the connection from your side. + +## How It Works + +Remote bridge creates a WebSocket bridge between your local Vite dev server and the deployed backend, allowing you to develop UI locally while using the deployed backend. + +```mermaid +flowchart LR + Browser[Browser] + Backend[Deployed Backend] + Bridge[WebSocket Bridge] + LocalVite[Local Vite Dev Server] + + Browser <-->|HTTPS| Backend + Backend <-->|WSS Tunnel| Bridge + Bridge <-->|HTTP/WS| LocalVite +``` + +### Details + +- The **Browser** connects to the deployed app backend with `?dev=true` or `?dev=` query parameter +- The **Deployed Backend** proxies UI requests through a WebSocket tunnel (`/dev-tunnel`) to your local machine +- The **WebSocket Bridge** (running locally) receives fetch requests and file read requests from the backend +- The **Local Vite Dev Server** serves the UI files and provides hot module replacement (HMR) +- The bridge sends responses back through the WebSocket to the backend, which serves them to the browser + +### What Gets Hot-Reloaded + +With remote bridge you get instant hot-reload for: + +- **UI Changes** - Any changes to your React/TypeScript/CSS files in the `client/` directory +- **Query Files** - SQL files in the `config/queries/` directory (`.sql` files only) + +Backend code is **not** hot-reloaded. You need to redeploy your app to see changes in the backend code. diff --git a/docs/docs/index.md b/docs/docs/index.md index adcaedd7..87e2f001 100644 --- a/docs/docs/index.md +++ b/docs/docs/index.md @@ -4,6 +4,8 @@ sidebar_position: 1 # Getting Started +import Prerequisites from './_prerequisites.mdx'; + ## Introduction AppKit is a TypeScript SDK for building production-ready Databricks applications with a plugin-based architecture. It provides opinionated defaults, built-in observability, and seamless integration with Databricks services. @@ -16,10 +18,7 @@ AppKit simplifies building data applications on Databricks by providing: - **Developer experience**: Remote hot reload, file-based queries, optimized for AI-assisted development - **Databricks native**: Seamless integration with SQL Warehouses, Unity Catalog, and other workspace resources -## Prerequisites - -- [Node.js](https://nodejs.org) -- Databricks CLI: install and configure it according to the [official tutorial](https://docs.databricks.com/aws/en/dev-tools/cli/tutorial). + ## Quick start options @@ -40,50 +39,51 @@ Install the Databricks MCP server and configure it for use with your preferred A databricks experimental apps-mcp install ``` -Once configured for your development environment, you can use your AI assistant to create and deploy new Databricks applications, as well as to iteratively evolve your app’s codebase. +Once configured for your development environment, you can use your AI assistant to create and deploy new Databricks applications, as well as to iteratively evolve your app's codebase. + +Just prompt your AI assistant to create a new Databricks app, such as: -The MCP server exposes the following capabilities: +``` +Create a new Databricks app that displays a dashboard of the nyc taxi trips dataset. +``` -- **Data exploration**: Query catalogs, schemas, tables, and execute SQL -- **CLI command execution**: Run bundle, apps, and workspace operations -- **Workspace resource discovery**: Inspect and navigate workspace resources +To learn more about the MCP server, see the [AI-assisted development](./development/ai-assisted-development.mdx) documentation. ## Manual quick start Learn how to create and deploy a sample Databricks application that uses AppKit with the Databricks CLI. -### Create a new Databricks app +### Bootstrap a new Databricks app -Run the following command to create a new Databricks application: +Run the following command to bootstrap the new Databricks app with AppKit: ```sh -databricks apps create {application-name} +databricks experimental dev app init ``` -This creates a new Databricks application named `{application-name}` in the current workspace. - -### Bootstrap the app codebase with AppKit +Follow the prompts to bootstrap the app codebase in the current working directory. -Run the following command to bootstrap the app codebase: +The command will guide you through the process of: +- creating a new Databricks app +- scaffolding the app codebase with selected features +- installing dependencies +- (optionally) deploying the app to Databricks +- (optionally) running the app in development mode -```sh -databricks experimental appkit init -``` - -Follow the prompts to bootstrap the app codebase in the current working directory. -This creates a complete TypeScript project with Tailwind CSS, React, and AppKit installed out of the box. +Learn more about the various [development flows](./development/) available with AppKit. ### Deploy the app to Databricks Run the following command to deploy the app to Databricks: ```sh -databricks experimental appkit deploy . +databricks experimental dev app deploy . ``` This deploys the sample app to Databricks. ## Next steps -- **[Core Concepts](./core-concepts/principles)**: Learn about AppKit's design principles and architecture +- **[App Management](./app-management.mdx)**: Manage your AppKit application throughout its lifecycle using the Databricks CLI - **[API Reference](./api/appkit/)**: Explore the complete API documentation +- **[Core Concepts](./core-principles)**: Learn about AppKit's design principles and architecture diff --git a/docs/src/pages/contributing.md b/docs/src/pages/contributing.md index 6a82051c..79be87ec 100644 --- a/docs/src/pages/contributing.md +++ b/docs/src/pages/contributing.md @@ -6,7 +6,7 @@ AppKit is an [Apache 2.0 licensed](https://github.com/databricks/appkit/blob/mai Follow our [contribution guidelines](https://github.com/databricks/appkit/blob/main/CONTRIBUTING.md) for code contributions, setup instructions, and DCO requirements. -Before contributing, review our [Core Principles](/docs/core-concepts/principles) to understand AppKit's design philosophy and guiding principles. +Before contributing, review our [Core Principles](/docs/core-principles) to understand AppKit's design philosophy and guiding principles. ## Documentation Contributions From f8888e1b893acbab491ee2d9013a28354a60a911 Mon Sep 17 00:00:00 2001 From: Pawel Kosiec Date: Thu, 15 Jan 2026 11:02:39 +0100 Subject: [PATCH 2/2] chore: improve docs after review --- docs/docs/app-management.mdx | 96 +++++++++---------- .../development/ai-assisted-development.mdx | 8 +- docs/docs/development/local-development.mdx | 2 +- docs/docs/development/remote-bridge.mdx | 14 +-- docs/docs/index.md | 6 +- 5 files changed, 60 insertions(+), 66 deletions(-) diff --git a/docs/docs/app-management.mdx b/docs/docs/app-management.mdx index 32aa41ae..e2a59765 100644 --- a/docs/docs/app-management.mdx +++ b/docs/docs/app-management.mdx @@ -4,13 +4,13 @@ sidebar_position: 3 import Prerequisites from './_prerequisites.mdx'; -# App Management +# App management Manage your AppKit application throughout its lifecycle using the Databricks CLI. This guide covers deploying, starting, stopping, monitoring, and deleting apps. -## Create App +## Create app See the [Quick start](./index.md#quick-start-options) section to create a new Databricks app with AppKit installed. @@ -23,12 +23,12 @@ Before deploying your app, configure it according to your needs. See the [Databr - Authorization and permissions - Networking configuration -## Deploy App +## Deploy app Deploy your AppKit application using the automated deployment pipeline: ```bash -databricks experimental dev app deploy +databricks apps deploy ``` This command runs a complete deployment pipeline: @@ -40,43 +40,37 @@ This command runs a complete deployment pipeline: For all available options, run: ```bash -databricks experimental dev app deploy --help +databricks apps deploy --help ``` ::: ### Examples -Deploy to the default target: +- Deploy to a specific target: -```bash -databricks experimental dev app deploy -``` + ```bash + databricks apps deploy --target prod + ``` -Deploy to a specific target: +- Deploy with custom variables: -```bash -databricks experimental dev app deploy --target prod -``` + ```bash + databricks apps deploy --var="warehouse_id=abc123" + ``` -Deploy with custom variables: +- Skip the build step for faster iteration: -```bash -databricks experimental dev app deploy --var="warehouse_id=abc123" -``` + ```bash + databricks apps deploy --skip-build + ``` -Skip the build step for faster iteration: +- Force deploy (override Git branch validation): -```bash -databricks experimental dev app deploy --skip-build -``` - -Force deploy (override Git branch validation): - -```bash -databricks experimental dev app deploy --force -``` + ```bash + databricks apps deploy --force + ``` -## Start App +## Start app To start a stopped app, run: @@ -84,7 +78,7 @@ To start a stopped app, run: databricks apps start {name} ``` -## Stop App +## Stop app Stop a running app without deleting it: @@ -104,7 +98,7 @@ databricks apps list databricks apps get {name} ``` -## Stream App Logs +## Stream app Logs Stream application logs in real-time: @@ -118,37 +112,37 @@ By default, this shows the most recent 200 log lines and exits. ### Examples -Show the last 50 log lines: +- Show the last 50 log lines: -```bash -databricks apps logs my-app --tail-lines 50 -``` + ```bash + databricks apps logs my-app --tail-lines 50 + ``` -Follow logs with a search filter: +- Follow logs with a search filter: -```bash -databricks apps logs my-app --follow --search ERROR -``` + ```bash + databricks apps logs my-app --follow --search ERROR + ``` -Filter logs by source: +- Filter logs by source: -```bash -databricks apps logs my-app --follow --source APP -``` + ```bash + databricks apps logs my-app --follow --source APP + ``` -Save logs to a file: +- Save logs to a file: -```bash -databricks apps logs my-app --follow --output-file app.log -``` + ```bash + databricks apps logs my-app --follow --output-file app.log + ``` -Stream logs for 5 minutes: +- Stream logs for 5 minutes: -```bash -databricks apps logs my-app --follow --timeout 5m -``` + ```bash + databricks apps logs my-app --follow --timeout 5m + ``` -## Delete App +## Delete app Permanently delete an app: diff --git a/docs/docs/development/ai-assisted-development.mdx b/docs/docs/development/ai-assisted-development.mdx index 20e707ca..20ae72d7 100644 --- a/docs/docs/development/ai-assisted-development.mdx +++ b/docs/docs/development/ai-assisted-development.mdx @@ -4,13 +4,13 @@ sidebar_position: 2 import Prerequisites from './_prerequisites_app.mdx'; -# AI-Assisted Development +# AI-Assisted development AppKit integrates with AI coding assistants through the Model Context Protocol (MCP). -## Installing MCP Server +## Installing MCP server To install the Databricks MCP server for your preferred AI assistant, run: @@ -18,7 +18,7 @@ To install the Databricks MCP server for your preferred AI assistant, run: databricks experimental apps-mcp install ``` -## MCP Capabilities +## MCP capabilities The MCP server exposes the following capabilities for AI assistants: @@ -49,7 +49,7 @@ Here are some basic examples you can use to explore your app and workspace: Possibilities are virtually endless. Ask your AI assistant to help you with your app and workspace. -## LLM Resources +## LLM resources AppKit provides specialized guidance files to help AI coding assistants work more effectively with the projects. diff --git a/docs/docs/development/local-development.mdx b/docs/docs/development/local-development.mdx index 7d995bb2..d2d56de8 100644 --- a/docs/docs/development/local-development.mdx +++ b/docs/docs/development/local-development.mdx @@ -4,7 +4,7 @@ sidebar_position: 1 import Prerequisites from './_prerequisites_app.mdx'; -# Local Development +# Local development diff --git a/docs/docs/development/remote-bridge.mdx b/docs/docs/development/remote-bridge.mdx index f7f086e6..013ba889 100644 --- a/docs/docs/development/remote-bridge.mdx +++ b/docs/docs/development/remote-bridge.mdx @@ -10,7 +10,7 @@ import Prerequisites from './_prerequisites_app.mdx'; Remote bridge allows you to develop against a deployed backend while keeping your UI and queries local. This is useful for testing against production data or debugging deployed backend code without redeploying your app. -## When to Use Remote Bridge +## When to use Remote Bridge Use remote bridge when: - Testing against production data @@ -18,16 +18,17 @@ Use remote bridge when: - Developing UI without running backend locally - Collaborating with team members on the same backend -## Starting and Stopping the Remote Bridge +## Starting and stopping Remote Bridge To start the remote bridge, run the following command: ```bash -databricks apps dev-remote --app-name my-app --client-path ./client +databricks apps dev-remote ``` The command will: +1. Obtain app name from the context (either `app.yml` file or user input in the CLI) 1. Start a local Vite development server 2. Establish a WebSocket bridge to your deployed app 3. Provide two URLs: @@ -35,7 +36,6 @@ The command will: - **App URL**: Direct link for your own use (`?dev=true`) - **Shareable URL**: Link with tunnel ID for sharing with team members (`?dev=`) - :::note For all available options, run: @@ -46,13 +46,13 @@ databricks apps dev-remote --help To stop the remote bridge, press `Ctrl+C` in the terminal. -## Connection Approval +## Connection approval When you start remote bridge, every time you open the URL in your browser from a new device, you'll be prompted to approve the connection. You can provide the URL to your team members to allow them to see the app in their browser. You will still need to approve the connection from your side. -## How It Works +## How it works Remote bridge creates a WebSocket bridge between your local Vite dev server and the deployed backend, allowing you to develop UI locally while using the deployed backend. @@ -76,7 +76,7 @@ flowchart LR - The **Local Vite Dev Server** serves the UI files and provides hot module replacement (HMR) - The bridge sends responses back through the WebSocket to the backend, which serves them to the browser -### What Gets Hot-Reloaded +### What gets hot-reloaded With remote bridge you get instant hot-reload for: diff --git a/docs/docs/index.md b/docs/docs/index.md index 87e2f001..2350b914 100644 --- a/docs/docs/index.md +++ b/docs/docs/index.md @@ -2,7 +2,7 @@ sidebar_position: 1 --- -# Getting Started +# Getting started import Prerequisites from './_prerequisites.mdx'; @@ -58,7 +58,7 @@ Learn how to create and deploy a sample Databricks application that uses AppKit Run the following command to bootstrap the new Databricks app with AppKit: ```sh -databricks experimental dev app init +databricks apps init ``` Follow the prompts to bootstrap the app codebase in the current working directory. @@ -77,7 +77,7 @@ Learn more about the various [development flows](./development/) available with Run the following command to deploy the app to Databricks: ```sh -databricks experimental dev app deploy . +databricks apps deploy ``` This deploys the sample app to Databricks.