Deployment Lifecycle

When you run de deploy, Dash Enterprise:

  1. Pushes the app code to a remote Git repository.
  2. Starts the build process, which fetches the code from the repository.
  3. Detects the pip buildpack by discovering the requirements.txt file in the app root.
  4. Installs the Python version selected by your administrator. Or, if you have specified a different Python version in your app Settings, Dash Enterprise installs that one instead.
  5. If an Aptfile file is provided, Dash Enterprise installs the specified APT packages.
  6. Installs the Python dependencies specified in the requirements.txt file.
  7. If a project.toml file is provided and it contains a predeploy field, Dash Enterprise runs the specified predeploy script.
  8. Creates the image and uploads it to the container registry.
  9. Based on the image, Dash Enterprise creates containers using the containerd runtime.
  10. Runs the commands as specified in Procfile in the appropriate container(s) to start the app, job queue, or background process.
  11. If a project.toml file is provided and it contains a postdeploy field, Dash Enterprise runs the specified postdeploy script.
  12. Releases the app, opening it to web traffic.
  13. Cleans up old containers and images.

When you run de deploy, Dash Enterprise:

  1. Pushes the app code to a remote Git repository.
  2. Starts the build process, which fetches the code from the repository.
  3. Detects the Conda buildpack by discovering the environment.yml file in the app root.
  4. Installs Miniconda.
  5. If an Aptfile file is provided, Dash Enterprise installs the specified APT packages.
  6. Installs the Python dependencies specified in the environment.yml file.
  7. If a project.toml file is provided and it contains a predeploy field, Dash Enterprise runs the specified predeploy script.
  8. Creates the image and uploads it to the container registry.
  9. Based on the image, Dash Enterprise creates containers using the containerd runtime.
  10. Runs the commands as specified in Procfile in the appropriate container(s) to start the app, job queue, or background process.
  11. If a project.toml file is provided and it contains a postdeploy field, Dash Enterprise runs the specified postdeploy script.
  12. Releases the app, opening it to web traffic.
  13. Cleans up old containers and images.