Overview

This documentation is for Dash Enterprise.
Dash Enterprise is the fastest way to write & deploy Dash apps and
Jupyter notebooks.
10% of the Fortune 500 uses Dash Enterprise to productionize AI and
data science apps. Find out if your company is using Dash Enterprise

Your app project structure, the files you include in your project folder and their content, determines how Dash Enterprise builds, deploys, and releases your apps and workspaces. Some files are required to be present in your project for an app to build and deploy on Dash Enterprise. For example, along with your app’s code, a basic project needs a file specifying your app’s dependencies, and a Procfile to launch its web process. These files can be configured in different ways and you can add additional files to configure other aspects of the build and deployment.

The structure of your project will depend on:

• The buildpack you want to use. Buildpacks are the technology responsible for transforming deployed code into the image that is then run as containers on Dash Enterprise. Dash Enterprise supports pip and Conda buildpacks, and each buildpack requires different files.
• How you want to configure the build and deployment. For example, if you want to change your app’s Python version or use predeploy scripts.
• The type of app. Dash and Streamlit have different project structures and require different configuration in some files.

Table of Contents

• Dash App Structure - The structure of a Dash app and how to configure the buildpack and other aspects of the build and deployment.

• Streamlit App Structure - The structure of a Streamlit app and how to configure the buildpack and other aspects of the build and deployment.

• Django App Structure - The structure of a Django app and how to configure the buildpack and other aspects of the build and deployment.

• Deployment Lifecycle - What happens when you run de deploy to deploy an app to Dash Enterprise.